Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

182 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you