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

[Samuel Chow]

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?

[Gabriel Ribeiro · Accepted solution]

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.

thanks.