Symptoms
- Build B has a Finish Build Trigger tracking Build A.
- Build B does not have a Snapshot Dependency on Build A.
Once Build A finishes successfully, the Finish Build Trigger triggers Build B except for the cases when Build A is a history build.
Cause
Ignoring history builds in Finish Build Trigger is by design.
Resolution
To work around this limitation, change the Finish Build Trigger to the VCS or Schedule Trigger and add a Snapshot Dependency in Build B on Build A. Disable the Do not run new build if there is a suitable one option.
This will ensure that every time before Build B runs, Build A runs first. The drawback is that you won't be able to start Build B without starting Build A first unless you change the Snapshot Dependency options.
Additional information
Related issue: Finish Build Trigger not working on History Build
Comments
0 comments
Please sign in to leave a comment.