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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,457,480
Community Members
 
Community Events
176
Community Groups

How to turn off deployment concurrency control when using multiple runners to build dev branches

I want to turn off deployment concurrency control (the pipeline pause) for our developer branches.

I am a company

I want my developer's individual commits to build simultaneously on multiple self-hosted runners

So that there is no resource contention when I employ more than one developer

1 answer

1 accepted

3 votes
Answer accepted

Hi Christopher,

If your developers are working on individual developer branches the pipelines would continue to build separately/concurrently.

However, if they are committing to a common `development` branch, then the concurrent builds are paused. The support page doesn't mentioned any setting to disable this. This is probably done to prevent multiple deployments to the same environment, so it's more of a safeguard against race conditions.

We were using deployment: Development in order to substitute environment variables so the build would correctly substitute these values in artifacts. Doing some yaml-foo and removing the deployment from the build step and adding it to the step for develop only allowed us to do multiple simultaneous builds. Thank you.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events