Home/ Questions/Q 6077039
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T10:40:34+00:00

We have 2 project configurations A and B . B depends on A .

  • 0

We have 2 project configurations A and B. B depends on A. A commiter makes a change in project A that causes build failure in downstream project B.

Is there a way in TeamCity to notify the commiter of project A that the B has failed because of his change?

Jenkins/Hudson supports that using upstream-individuals:A as an email address in this particular situation.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I tried to set it up through snapshot dependencies as Danere pointed out and it is working. Since the TC way is different from what you probably tried with Jenkins here is my setup:

    1. I added another project to the chain named C that contains 2 VCS: projectA and projectB and a dummy build step.
    2. Project C is configured to be triggered by any VCS change
    3. Project C has a snapshot dependency on project B
    4. Project B has a snapshot dependency on project A
    5. Both project A and B do not have any triggers.

    The project C could be probably eliminated but my configuration is more complex and the last step performs system tests and I didn’t want it to monitor all VCSs of all the upstream projects.

    • 0