Bamboo leaves multiple agents idle when there are builds queued.

[PeterL]

We have 4 agents enabled on our build server, and bamboo will build up to 4 plans concurrently, but there seems to be a lot of lag between builds queuing and the agents starting (we have seen 6+ builds queued and all 4 agents idled).

[Y]

I have been working with Bamboo support and they were able to reproduce the issue.  A bug has been created to fix this issue, please vote and watch the issue.

https://jira.atlassian.com/browse/BAM-15187 

[Mark Bockstael]

We see the same lagging happening. Even when manually starting a build when an agent is idle, it takes up to 5 minutes before it actually starts. The agent log shows : 2014-11-06 11:26:19,463 INFO [2-BAM:: .....] [com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl] Agent 7831553 checking build queue for executables... 2014-11-06 11:31:19,556 INFO [2-BAM:: .....] [com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl] Agent 7831553 checking build queue for executables... 2014-11-06 11:36:19,651 INFO [2-BAM:: .....] [com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl] Agent 7831553 checking build queue for executables... Any idee how this build queue check can be done more frequently?

[Y]

Was there a resolution for this? i recently upgraded from 3.2.2 to 5.6.2 and i am seeing the same thing, there are multiple jobs queued and multiple agents idled. In 3.2.2 all agents would run any queued jobs, they all have the same capabilities.

[Matt]

Have you check project dependency on agent capabilities? Maybe there is for example one agent capable to run this build.