Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Override Concurrent Build Setting At Stage or Job Level

Hi all,

Is it possible to set a plan to allow concurrent exexecution of stages or jobs?

I have a changeset build process (like a gated checkin build but we build after the checkin). At present, we use a bunch of scripts and three plans:

- Process queue for next changeset

- Run Build

- Finalize Results

I'd like to setup one plan and manage the rest inside it. I believe I can only set concurrent build limits at the plan level so I'll need to set this up as follows:

- Process-queue-plan manages incoming queue of changeset to run and starts Run-Build-Plan (concurrent limit = 1)

- Run-Build-Plan builds specific revision in JOB1 and then finalizes in JOB2 (concurrent limit = many)

Please let me know if I'm right in my understanding that concurrency is per plan and not per start or job.

Thanks

Peter

1 answer

0 votes

It's true that concurrency limit is per plan, but it doesn't mean you can't achieve what you want ;-)

If I understand correctly "Process queue for next changeset" does sth like the following:

- check if there are new commits in source repo(s) (and this needs to be one-at-a-time thing)

- spawn a process that will run 2 build steps. (there can be many of those processes)

Here's the thing: this is exactly what Bamboo can do for you.

Set up a plan, configure "Repository polling"* automatic trigger and add your 2 stages to the plan**. Set up concurrency limit to whatever you want. Done.

Internally, the triggering build logic uses an exclusive lock, so even though Jobs will run in paraller, only one 'triggering process' will run at a time, regardless of concurrency setting.

*) there are other options too ;-)

**) Actually your 2 build scripts might be better mapped to single Bamboo Job with many Tasks rather to 2 Stages, depending on how your scripts interact. For example: are they supposed to run in the same dir? If so, Tasks are better choice. More on this: https://confluence.atlassian.com/display/BAMBOO/Using+stages+in+a+plan

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Industry Groups

🤖 A Jira Senior Developer's thoughts on remote pair programming

Hello, Tech enthusiasts! Are you ready for October to begin 🙀? I wanted to share with you an Article I came across from Work/Life (The Atlassian blog) from  a senior developer on the Jira te...

36 views 1 2
View post

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