Is there a way to set job execution in a stage

[Eugene Jiang]

I've got a plan that has a few stages, one of the stage is a testing stage, within that stage I've got 25 jobs which means requires 25 agents if I want to execute them all in parallel. But because some of the job actually run pretty fast like less than 5 mins, and some are long like 90 mins. So obviously instead of having 25 agents i've put down 20 (remote agent btw). But the problem is that I don't know how to control the order these 20 jobs gets run. So it end up with 2 of the longest job didn't get into execution at the first batch, in fact they were executed last after waited for 30 mins to have a free agent available.

So my question is there a way to configure these long running job to start in the first, and then for other fast running jobs, they can wait till others finishes. Thanks!

[Ayrijit Swain]

Hi Eugene,

In a Bamboo plan, the Stages run in sequence, Jobs run in parallel. and Tasks inside a job runs in sequence. There is no explicit way to order the Jobs, bamboo does it randomly based on the build queue and agents available.  suggestion would be and if you can optimize and club short-running jobs so that all the jobs takes more or less similar time to finish and can effectively use all the 20 agents together.

Please refer to KB articles below for additional reads on this topic.

> https://confluence.atlassian.com/bamboo/using-stages-in-a-plan-289276862.html 

> https://confluence.atlassian.com/bamboo/jobs-and-tasks-289277035.html

[Eduardo Alvarenga]

Hello @Eugene Jiang,

Welcome to Atlassian Community!

On top of @Ayrijit Swain's comment, you can also consider using Dedicated Agents.

Dedicated Agents allow you to always have them available to the long builds while other non-dedicated Agents would be used on the other short builds, on recycled Agents.

Best regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--