Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is there a way to modify the way builds are queued on bamboo?

We currently have 10 remote agents. 5 could be offline when its code freeze. 

We normally have 5 agents up and accepting builds and when we have a long list that joins the queue, +10 plus waiting builds. We obviously bring the other 5 up to assist. In doing so, it seems at this point FIFO has already been applied and the waiting builds never go to the agents that just came up and they just stay IDLE.

The same happens when we have agents dedicated to larger builds and then undedicate them when there are long waiting build queue to help. The just stay IDLE and the queue waits for the Agents that were presently there. 

Now how do we change the way queuing process in this regard?




1 answer

0 votes

Hi Kuhle,

Normally Bamboo should automatically dispatch the queued builds to any available agent, even if that agent only came online after the build was started. This suggests that something's not working as expected.

I'd look at the logs on the Bamboo server (in <BambooHome>/log/atlassian-bamboo.log) should show lines like the following repeatedly:

[BuildAgentControllerImpl] Agent 163841 checking build queue for executables...

The ID would be different, matching the ID of one of the idle remote agents.



Premier Support Engineer


Hi Christian. 

They currently do dispatch to the agents.. that process is fine. its only when items are already sitting in the queue.. assuming that means they are assigned to a specific agents on the queue at tht point. Then we undedicate agents which were dedicated. those new ones will stay IDLE and not grab anything from the queue. Even if there are 100 builds at that point waiting to build.


Instead they will accept newly triggered builds and wont let those join the queue.

Jeyanthan I Atlassian Team Feb 05, 2018

Could it be that the requirements and capabilities for those builds are not met by these newly started agents?

What is the version of Bamboo you are working on?

All capabilities are met.. If the agents were up before the builds got queued, they run on these agents.. no problem.

im on ver 6.2.1 build 60208

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events