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,455,373
Community Members
 
Community Events
175
Community Groups

Why do bitbucket branch list show failing build for a bamboo build that ran on a different branch?

Edited

So I have this setup...

Bamboo:

 - I have a plan that does a series of actions

 - the plan is linked to a repository

 - the default branch is set to master

 - the plan is configured to do automatic branch creation for new branches

 - now when i run the plan, it uses the default branch which is master

bam-1.png

Then....

 

BitBucket:

 - I have a repo linked to that build plan above

 - I go to the list of branches

 

This view shows me the failing and passing builds linked to this repo. Naturally I would see that a build has either passed or failed for master which has just finished running.

 

What I don't understand is all the "plan branches" i have on the bamboo plan also shows the same result.

 

I'm under the impression that bitbucket branches would only pick up builds that ran on the same branch.

 

bam-2.png

I didnt show the failing builds popup to save this post from clutter but it does show the same build.

 

I'm expecting the branches list to show only build results that ran for a corresponding branch so that would be:

 

master - 1 failing build

branch-1 - no builds

branch-2 - no builds

branch-3 - no builds

 

What's wrong with my setup?

2 answers

1 accepted

1 vote
Answer accepted

Hi @iamkenos

First of all, I really want to thank you for the very detailed issue description. That is really,  helpful when we need to find out what is causing a problem.

There is nothing wrong with your setup. The problem is that Bamboo has more build status than the Bitbucket server and the status never built or not built are mapped to failed. That does not seem correct and because of that the following bug was open:

Please let me know if that explains what you see and if you have anything to add.

Hi @Daniel Santos 

 

That makes sense, thanks!

Just wanted to confirm though, on the linked bug, the use case was 'on build interrupt'. For the case above however, the build wasn't interrupted. It hasn't even triggered. Would the fix cater for that case too?

Hi @iamkenos

Yes, it should fix every possible scenario that leads to an unbuilt status. That status means that the build was triggered (manually or not) but it didn't even start a job when it was interrupted. It was in the phase of updating repository caches when something blocked it to move forward.

The steps to reproduce added to that bug are one of the many ways to cause that build status.

Let me know if that answers your question. =]

Like iamkenos likes this

Understood. Thanks!!

Like Daniel Santos likes this

You are welcome! =]

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events