nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Kuhle Nkondeshe

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?

Thanks

Accepted answers

All comments

Christian Glockner

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.

Cheers,

Christian

Premier Support Engineer

Atlassian

Kuhle Nkondeshe

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

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?

Kuhle Nkondeshe

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

bitbucket

bamboo