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,461,804
Community Members
 
Community Events
176
Community Groups

PR Merge Rules for Failed Builds are Broken

We are running Azure Dev Ops and Snyk, which are linked to Bitbucket and appear correctly on our PRs.  But I've run into a problem with the build rules.

The rules are '1+ build passed', and 'No failed builds'.  I cannot seem to find where those rules are configured, but they are fine for what we want to do.  My problem is that I have a Green Snyk build, and had a failed Azure Dev Ops build.  When I started a new build on Azure Dev Ops (there was a network error, so I re-ran the failed jobs), the build shows in the PR as 'In Progress'...but it is being treated as a Success and the 'This Pull Request is Ready to Merge' button has appeared, along with all Green ticks in the Checks Passed section.

I feel like the 'In Progress' should be treated like a Failure, until it is complete yeah?  What are other people's thoughts?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events