Two master branches on auto-managed git branches plan

I have the following problem or inconvenience:

On a bamboo instance on which I have projects that checkout from git repositories (from stash) when I create the auto-detected branches from stash I end up with two master branches.
In git we have at least one branch called "master" and if needed some additional release, devel, feature, etc branches.

The problem is that even on project with one branch - "master", when I add in bamboo the branch from git I end up with two branches in the branch list.

The first one can be found on http://<bamboo-url>/browse/PROJECT-PLAN
The second one is usually on http://<bamboo-url>/browse/PROJECT-PLAN0

Is there a way of disabling one of them or having in the begining only one ?

The branch imported from stash/git and added to bamboo and can be renamed.
But in the end it is not a solution to have one "master" and one "real-master" .

1 answer

Apparently the problem has been signaled before in https://jira.atlassian.com/browse/BAM-12789

However, my main problem as a result of the problem signaled above is that when I run the plan manually, only the plan is executed (but none of the branches)

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

474 views 2 5
View question

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you