"Move to top" button breaks chains
Hello everyone,
We have a unpleasant problem with build chains:
in chain of three build all work fine, until someone dont use button "Move to top" on the build from the same buildType. In this case another build starting between builds from chain and rewrite results of first build
Normal pipeline work: Build A -> Build B - Build C
In this case: Build A -> Build A1 -> Build B -Build C, and we have results from build A1, not A
In snapshot dependency documentation i cannot find a solution, maybe someone have any idea?
Please sign in to leave a comment.
Hi! What are the differences between Build A and Build A1? Do they check out different revisions or have different customized parameters?
TeamCity's build queue optimization mechanism can merge queued dependencies if they check out the same revision of code and don't have different customized parameters (some other conditions also need to be met in order for this to happen, but those two are the most prominent ones).
Differences between Build A and Build A1 in type of build. A - dev build of project, A1 - RC build of project. In this case B and C build - signing build and upload build to Firebase respectively.
All this build have different chains and different names/IDs, some different params. In this case we look the next issue: Builded project from Develop build, then RC build rewrite all results and signing&uploading wrong app to Firebase.