Dependency and the queue top
Let' consider build A that compiles a project and build B that runs test. Build A is a snapshot dependency of build B.
Assume, that build A was queued. Than build B was queued with "put the build to the queue top" option.
Will it put build A to the queue top in the current version of TeamCity?
Please sign in to leave a comment.
A will definitely be at the top of the queue, the question would be whether it would be the pre-existing one or the new one that triggering B would spawn. It will depend on whether TeamCity considers that it can replace the new version of A with the queued one or not. TeamCity will understand that B needs A so B will never run before any of the two possible instances of A, but for the previous A to be replaced so that B can reuse it, TeamCity has to consider them equivalent (same set of parameters, same revisions, etc)
Triggering B with "put to the top" should put the new A in front of the old in case they aren't considered equivalent, triggering with the option is equivalent to manually pushing to the top using the action explained here: https://www.jetbrains.com/help/teamcity/ordering-build-queue.html#OrderingBuildQueue-ManuallyReorderingBuildsinQueue