Branch pipeline halts on multiple merged PRs “Another pipeline is deploying to devops-test”

[Ankit Solanki]

Hi Bitbucket team / Community,

I am facing an issue with my Bitbucket pipelines where branch deployments halt when multiple PRs are merged, even though concurrency groups are configured.

Here’s my scenario:

1. I have PR pipelines that run Salesforce validation . These pipelines run per PR branch, and concurrency works perfectly — if multiple PRs trigger validation at the same time, they queue and auto-resume once previous builds finish.

2. I also have branch pipelines for deployments (Salesforce + Vlocity) on a branch called ankit_vlocity.

   definitions:

     steps:

   
   

       - step: &sf-validate

           name: Validate Salesforce (Delta)

           script:

             - ./cicd-scripts/validateDeployment.sh

           concurrency-group: salesforce-validation-${BITBUCKET_BRANCH}

   
   

       - step: &sf-deploy

           name: Deploy Salesforce (Delta)

           script:

             - ./cicd-scripts/deploySalesforce.sh

           concurrency-group: salesforce-deployment

   
   

       - step: &vlocity-deploy

           name: Deploy Vlocity (Delta)

           script:

             - ./cicd-scripts/deployVlocityDelta.sh

           concurrency-group: vlocity-deployment

   
   

   pipelines:

     pull-requests:

       "**"

             - step:

                 <<: *sf-validate

                 name: Salesforce Validation

                 deployment: devops-test

   
   

     branches:

       ankit_vlocity:

         - stage:

             name: Deploy to DevOps-Test

             deployment: devops-test

             steps:

               - step:

                   <<: *sf-deploy

                   name: Salesforce Deployment

               - step:

                   <<: *vlocity-deploy

                   name: Vlocity Deployment

   
   
   
   

   Problem:

   • When multiple PRs are merged to ankit_vlocity, the branch pipeline triggers multiple deployments for the same branch.

   • The pipeline initially shows as waiting, then moves to Halted stage with this message:

   Halted This pipeline was halted because another pipeline was deploying to devops-test.

   • I tried setting a global concurrency group (e.g., concurrency-group: vlocity-deployment) instead of using ${BITBUCKET_BRANCH}, but the problem persists.

   Observations:

   • PR validation pipelines queue and auto-resume properly, likely because each PR has its own branch concurrency queue.

   • Branch deployments halt because multiple pipelines are triggered for the same target branch/org, and Bitbucket seems to queue the entire stage, which blocks the pipeline from auto-resuming.

   Questions:

   1. Why does the branch deployment halt even when a global concurrency group is used?

   2. Is there a recommended way to configure concurrency so that multiple merged PRs deploying to the same branch/org queue properly and auto-resume?

   3. Would splitting stages or changing concurrency behavior fix this issue, or is this expected Bitbucket behavior for branch pipelines?

   Any guidance or best practices would be greatly appreciated.

   Thanks in advance!

[Mark C]

Hi @Ankit Solanki

Thanks for reaching out to the community.

By default, you won't be able to run builds simultaneously on the same deployment environment.

Note: you can only have one in-progress deployment in each environment. Any later pipelines that deploy to the same environment will be automatically paused. You can manually resume the paused deployment step once the in-progress deployment completes.

May I know why you'd need to deploy using PR trigger?

Regards,
Mark C

[Ankit Solanki]

Hi @Mark C ,

Whenever our PR is open it always run Salesforce Validation, Salesforce Deployment is triggered when our PR is merged to target branch i.e. any changed being merged to target branch triggeres deployment as we want to deploy only delta changes which were part of PR.

I want to understand best practices or suggestion to tackle my scenario, where build shouldn't go into queue. Will concurrency group not help?

[Ankit Solanki]

Additional context:

1. Branch deployments target the same environment (devops-test) and use stages, which seem to lock the environment per pipeline. This causes merged PRs to halt instead of queueing automatically.

2. We tried global concurrency groups, splitting stages into multiple steps, and manual triggers, but the problem persists.

3. Is there any way to configure branch deployments so that if another deployment is already running on the same deployment environment, the new deployment automatically goes into a queue and resumes when the previous one finishes? If not, are there any recommended workarounds to achieve this behavior?