No wait reason for some builds in the queue
TeamCity Professional 9.1.6 (build 37459)
Our build chain looks like this:
We have only one agent in this TC instance. What happens is this. We trigger the last job in the chain (queue test end), it puts all builds in the queue. While the first step runs (a sleep for X seconds), the queue test job, when queried from REST API as well as looking at build queue note for the build, shows 'Waiting for dependencies". That's expected. The unexpected is the queue test 2 job in the build queue does not have a note for waitReason. Why is this the case?
Thank you,
Denis
Please sign in to leave a comment.
Hi Denis,
Sorry for the delay. WaitReason is calculated asynchronously, so it can take a while until it appears.
I'm very interested in this. How long is "a while" usually? Just a rough ballpark, seconds, minutes, hours?
Hi James,
well, it will depend on a number of factors. It should be roughly between almost instantly and maybe a minute, but will depend on server load, size of a possible build chain, queue size, etc. and of course, on the reason itself. It's not that I was ambiguous with the "can take a while" for quickness, but because the time it can take might vary quite a lot.
Edit: It's likely that the best approach is to run a few tests on a test environment where you can replicate conditions and see how long it takes for your usual workflows.
I think we've seen longer times that that. However, we've got ~350 agents continuously doing work 24/7. So, maybe that attributes to the longer wait time for a reason?