You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Enable merge button in the pull request only after auto build success that too specific branch patterns. (branch level) ex: feature/XX_XX -->master PR only need to check the build status. If auto build is in progress, PR merge button should not enable.
Pls let me know if any option for this.
We have 500+ developers, will not wait for auto build to complete and merge the PR which leads wrong code to master branch which is golden source code
It’s a data centre /server
thank you so much for responding my message. Pls help me. Fyi
I don’t want minimum successful builds option because it’s a repo level.
I want at branch level… in multi branch pipeline we will only enable specific patterns., because developers volume is high. And we don’t have that much resources of build servers
I understand that you want to check for a successful build on branch (pattern) level, not on repository level before the PR merge button is enabled.
We have come across the same problem and have created an app that can be installed in Bitbucket to do exactly that and more.
With Workzone you can specify merge conditions, including successful builds, on branch level and block the merge button if the condition is not met. 
Enforce the (successful build) merge condition at repo level 
If you want to get really sophisticated you can set the merge-condition to auto-merge the PR as soon as the successful build result comes in from your CI system .
Let me know if that all makes sense.