Finish Build Trigger does not trigger the dependent project
I have two projects - A and B. A uses a VCS trigger for Git. B uses a Finish Build Trigger, waiting for a successful build of A.
After A is triggered and builds successfully, B does not trigger automatically.
If I then trigger B manually in the TeamCity UI, it will first trigger a new build of A (even if A just finished successfully).
The Triggers / Branch Filter for B is set to its default value of “+:<default>”. The Triggers / Branch Filter for A is set to its default value of “”.
I can check logs, but I don't know what I'm looking for.
Please sign in to leave a comment.
The most common build chain configuration, which works for most use cases, is the following:
1. B has a snapshot dependency on A.
2. B has a VCS trigger configured.
3. Once the B is triggered, it triggers A and waits for A to finish. B starts after A is finished.
This configuration doesn't use the Finish Build Trigger, as it is not required; triggering occurs via a snapshot dependency.
Please refer to the following documentation topics:
1. Snapshot dependencies: https://www.jetbrains.com/help/teamcity/snapshot-dependencies.html
2. Please note the "Do not run new build if there is a suitable one" setting. It allows reusing previously finished build A as a dependency of a newly triggered build B. However, only the suitable builds may be reused in such a manner: https://www.jetbrains.com/help/teamcity/snapshot-dependencies.html#Suitable+Builds
3. More information on build chains in TeamCity and examples: https://www.jetbrains.com/help/teamcity/build-chain.html
4. Finish build trigger has its use cases: https://www.jetbrains.com/help/teamcity/configuring-finish-build-trigger.html#Finish+Build+Triggers+and+Snapshots
Please let me know if you have any further questions.
Best regards,
Anton