Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Merging not allowed even after successful build

Merge was being prevented, and I thought that this may be due to the issue in Jenkins itself. After it's been resolved, forced builds succeeded, yet merge was still not enabled.

From this thread I gathered that the build count is attached to commits, not to the PR itself. So I have made a trivial change and committed it forcing a new build which was successful. The bitbucket PR page shows it as such, but yet the merge button still says "There is 1 issue preventing you from merging this pull request. You need a minimum of one successful build before this pull request can be merged."

I am puzzled. Any clues?

1 answer

1 accepted

0 votes
Answer accepted

Not sure if you're still experiencing the issue, but one option for troubleshooting is that you can update the status of the failed build over in the REST API.

If the latest commit in your PR is still this commit with a failed build, though, (even if another build was made against that commit that succeeded after the fact) we would expect that it couldn't be merged - as any failed build that hasn't been corrected by the integrated CI tool is assumed to be a result of an issue in the code, meaning that a new commit needs to pushed to the source branch of the PR to fix the code problem.

If this issue is still happening, feel free to post back the results from some of those REST API endpoints if you want help analyzing what you're getting back.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

769 views 15 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you