Hi,
it seems that we're experiencing a weird issue where a build started with a configuration that is impossible to build (since none of the agents matches the stage's requirement) blocks all other builds. All other builds are displaying the same message "Stage Awaiting Agent" even though we're sure those other builds can be build. When we stop/kill the blocking builds, all other builds start immediately.
An interesting thing to add here is all blocked builds are reporting the reason of the blocking build. E.g. All builds are using MsBuild 12.0; One build is set to 14.0 but none of the agents can run 14.0. The blocked build is reporting that none of the agents can run 14.0. Starting a second build here will wait as it looks blocked by the first build. When checking the reason for "awaiting" this build also reports that 14.0 isn't available, even when this build does not even use MsBuild 14.0.
Just want to make sure we're doing nothing wrong or otherwise would like to report this one as a possible bug.
We're using the latest version (1.7.1.65) ... All agents are compatible but not yet updated: All agents are running 1.7.1.54. (As it states compatible I assume this couldn't be the cause of this problem)
Kind regards, Remko Seelig