Put merge restriction via bitbucket pipelinIe, when we have more then one PR from same branch

Amit Kumar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 3, 2025

I have raised two PR from same source branch, if one of the build fails. we are not able to merge PR with success build.
I have enabled "Minimum number of successful builds for the last commit with no failed builds and no in progress builds"
any sujjestion we can achieve it .

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 4, 2025

Hi Amit,

Are you running pull-requests builds in Pipelines and is there a different pull-requests build for each PR?

The build status associated with each PR is posted to the last commit of the PR's source branch, which is why this merge check fails.

We have a bug report about this in our issue tracker with the request that only build statuses related to a specific PR are taken into account:

You can select the link This affects my team in the bug report to indicate you are affected by this issue. You can also add yourself as a watcher (by selecting the link Start watching this issue) if you'd like to get notified via email on any updates. Bug fixing is implemented as per our policy here and updates will be posted in the bug report.

In the meantime, the workarounds would be to:

  • temporarily disable the merge check to merge a PR
  • fix the issue on the PR with the failed build so that you get a successful build, and then both PRs could be merged

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events