bamboo auto plan branching limitations

if our git repositories are Stash embedded (created through the Stash interface), is auto plan branching in bamboo possible? Or must plan branches be manually created?

2 answers

1 accepted

0 votes
Accepted answer

I upgraded to Bamboo 5.5.0 and have had success with auto plan branching from our Stash Git repositories.

The only gotcha I encountered was needing to remove url patterns from the app links area in order for the linked repositories Stash repo communication to function (populate the drop-down list of available repos and branches). And, indeed, the url pattern I removed was no longer necessary to receive triggered updates from Stash. The url pattern was the only one present.. so, in effect, I removed all url patterns.

I'm a proponent of 5.5.0.

0 votes
Daniel Wester Community Champion Apr 21, 2014
You can specify a RegExp that will auto create the plan branches. But bamboo 5.5 is supposed to add more stash integration. Don't know what but it might be worthwhile to keep an eye out on it.

This does not really answer my question.

I understand that auto plan branching requires the entry of a regular expression for branch matching.

That capability is outlined on the doc page:

However, further down on that page, a limitations section exists which states auto plan branching "Cannot be used with the Git implementation embedded in Bamboo. (You need to have set up native Git.)".

Our Git implementation is embedded in Stash (setup through a Stash interface). I was wondering if the same limitation applies - we are unable to use auto plan branching as our Git implementation is embedded in Stash.

And hopefully, I have my terminology correct which is (loosely) -

native Git - a Git repo setup via Git command line

Git implementation embedded in Bamboo - a Git repo setup via Bamboo iface

Git implementation embedded in Stash - a Git repo setup via Stash iface

John - the fact that you're using Stash means that you don't have "Git
implementation embedded in Bamboo
", so you should be good.

We use Bamboo/Stash and have no issues with auto plan branch. Is your Bamboo not detecting new branches?

Yes, I understand that our implementation is not "Git implementation embedded in Bamboo". My supposition was that we have "Git implementation embedded in Stash" and I was questioning whether that carried the same limitations.

Regardless, the upgrade to 5.5.0 solved whatever auto plan branching issue we were experiencing. Auto plan branching is now working for us. Thank you for checking back on this.

We're on 5.3.0 and i've not seen any auto plan branching issue.

Curiously, did your issue occur consistently, random or only during certain workflow scenarios? I want to make sure we're not possibly overlooking an existing bug in versions < 5.5.0

I simply was not able to get it working. We were on version 5.4.2. I believe it was most likely a configuration issue. New branches in Stash were not auto-discovered. Also, pushes to an existing branch in Stash did not spawn the creation of the Bamboo branch. Are url patterns necessary for branch discovery at those versions(5.3.0, 5.4.2)? It is noteworthy that branches manually added were able to have builds triggered.

May have been a configuration thing. We don't specify any url patterns to detect our branches.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

936 views 3 9
Read article

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