Hello @vinod lalwani ,
Welcome to Atlassian Community!
As long as your AzureDevOps builds are reporting their status back to Bitbucket, meaning that you can see the status of your Azure builds on the bitbucket pull requests page, you could leverage Branch permissions to prevent the PR from being merged if the build in the more recent commit has reported a failure.
Among other restrictions you can implement in your repository with branch permissions, one of them is to suggest or require checks before a merge, where you can suggest/enforce specific conditions on merges for individual branches or branch patterns. For your case, there's a specific merge check that would apply: Check for {#} passed builds on the last commit and no failed builds. This merge check will warn/prevent the user from merging the pull request if the last commit in the pull request has failed or has not met the required number of successful builds.
So in this case, you could create a branch permission for the destination branch of your pull requests and enable the merge check above.
Please note that when you select any of these merge checks (and don't have the Premium plan), we'll just warn users when they have unresolved merge checks, but they'll still be able to merge. To prevent users from merging and enforce the completion of all merge checks you would have to upgrade to Premium and select Prevent a merge with unresolved merge checks. Learn more about Premium.
Hope that helps! Let me know in case you have any questions.
Thank you, @vinod lalwani .
Kind regards,
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.