We are using TeamCity 6.5.5 (very recent, 2 days ago we were on 6.5.4) and we have recently started using the build priority mechanism.
It seemed to work at first, but lately I've found that things with the highest priority possible go the the bottom of the queue. While looking at the documentation, I found this: (my bolding)
||This setting is taken into account only when a build is added to the queue. The builds with higher priority will have more chances to appear at the top of the queue; however, you shouldn't worry that the build with lower priority won't ever run. If a build spent long enough in the queue, it won't be outrun even by builds with higher priority.
This could explain why a high priority build still get at the bottom of the queue.
Could you elaborate as to how this work (how long is "long enough" before the priorities get bypassed?
), and possibly circumvented? I would really like my higher priority configurations to run before the others, no matter how long they have been stucked in the queue.