Hi,
We have 2 separate build servers, on each server we've installed 2 build agents. Using the "Tags" option, one agent handles gated checkin builds, the other Continuous Integration builds. So in total we can run 4 builds simultaneously (1 Gated build and 1 CI build on each machine).
Today I was testing a new build template for the CI build and disabled one of the agents that handles CI builds. This allows me to run a build when I want do a test-run without having to wait until other builds are finished. At the time I wanted to do a test-run, there were 3 builds running (2 gated checkins and one CI) and one gated checkin was queued.
First I enabled the CI build agent and then manually queued the build I was about to test. The problem is, this new build gets queued for no reason. After all there is 1 'CI build agent' available (since I just enabled it). It looks like the controller queues a build if the number of active+queued builds >= total available build agents. However in my situation there was a build agent available that could run my build. Can someone tell me if this is a bug in the TFS build controller?
Thanks!