Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,216
Community Members
 
Community Events
176
Community Groups

Enable merge button only after auto build success

Edited

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

1 answer

1 vote

Hello Geetha, welcome to the community!

Could you please specify which Bitbucket hosting type (cloud or datacenter/server) you are using? I can then try to help with more specific advice.

Thanks in advance, Ulrich

// Izymes

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

Hello Geetha,

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. [1]

Enforce the (successful build) merge condition at repo level [2]

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 [3].

Let me know if that all makes sense.

Best, Ulrich

 

[1] https://izymes.com/docs/workzone-merge-control-configure-automatic-pull-request-merge/

[2] https://izymes.com/docs/properties/

[3] https://izymes.com/docs/workzone-merge-control-test-driven-development-with-merge-control-and-continuous-integration/

Thanks for your time . It works for me. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events