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!


Is there a way to enable concurrent builds when deploying

We want to enable deploying concurrent builds to develop from different branches but no matter what we try bitbucket is pausing second build, anyone has any idea how to enable deploying as many concurrent builds as we want

1 answer

1 accepted

0 votes
Answer accepted
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 17, 2023

Hi @Ammar Karabeg and welcome to the community!

We have concurrency control in place because deploying multiple things to an environment can cause problems:

Could you perhaps explain why you want to do multiple concurrent deployments to the same environment? What are these builds doing, are they deploying to the same server?

Builds can run concurrently if you are deploying to different environments. You can also remove the keyword deployment: from a step; the builds will then also run concurrently but you won't be able to make use of the deployments features, and you may run into issues if you're deploying to the same location.

Kind regards,

Hey, thank you for the fast answer. The biggest problem we are having is that bitbucket is not letting us deploy new stuff to the environment even if the previous deployment is finished. A new pipeline gets paused and when we click on another pipeline is deploying link it navigates us to one that is done 

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 21, 2023

Hi @Ammar Karabeg,

Thank you for the info.

So, if you click on 'another pipeline' in build #1316, it takes you to pipeline #1308? This doesn't look right, as #1316 shows to have been triggered 31 minutes ago, while #1308 is from 3 days ago.

We have a bug where sometimes a deployment pipeline fails to unlock the deployment environment: However, even in this case, the lock should be removed automatically after a few hours.

Since your workspace is on a paid billing plan, I would suggest creating a support ticket for further investigation. I cannot access your repos and pipelines builds logs, but if you open a ticket, the engineer working on your ticket will be able to access them and investigate further.

You can create a ticket via, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. Please make sure to provide the URL of the builds and also mention that the 'another pipeline' link links to a deployment days before the current one. The support ticket will be visible only to you and Atlassian staff.

If you have any questions, please feel free to let me know.

Kind regards,

Like Ammar Karabeg likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events