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

How is job priority handled between plans with multiple remote agents?

If multiple plans each have multiple jobs, is the priority of job handled in such a way that all the plan that starts first has all of it's jobs put in the queue first, then whatever next plan is started has all of its job added to the queue? 

Some corner cases are remote agent capabilities must be available for the requirements of a job, so a job from another plan could be run first. Another corner case is users can manually edit build queues.

Am I missing anything?

1 answer

1 accepted

1 vote
Answer accepted
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 20, 2018

Hi Samuel,

The queue will be processed top-down based on agents availability. if you have a job that requires a specific capability that is only available in one agent and this agent is currently busy, it will be left in the queue until the agent becomes available but all other agents will continue processing all subsequent jobs:


In the gif above you'll see the behavior I mentioned, note that all jobs are being processed and the ones that have a specific requirement are left behind until the agent capable to build it becomes available.

If the user manually edits the queue, as expected, Bamboo will respect the new order but the same behavior from the example above will be persisted. 

Let us know you if you have other question.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events