Bamboo plan branching with multiple repos

I have a plan that uses 2 source repositories. Plan branching picks up the branches on the default repo but when it builds the other repo always checks out the same branch (master). I want the same branch on both repos.

I tried setting branch to ${bamboo.repository.git.branch} in the non-default repositories configutation so it would try to match the default repos branch but that didn't work.

How can I do this?

5 answers

This widget could not be displayed.

Very disappointing...

This widget could not be displayed.

At the moment the only option that works is (afaik) to manually define plan variable that points to the branch, and override it on each Plan Branch.

There's an improvement request you can vote on: https://jira.atlassian.com/browse/BAM-11544

Hi, Can you please explain in detail, how you implemented it?

This widget could not be displayed.

I just ran smack into this problem myself. I was thinking the only workaround would be to make a clone of the main plan, and configure the repositories for the branch I want. Alternatively, a script block could be used to checkout the right branch on each sub-repo.

I don't fully understand how a plan variable could be used to specify the branch, though.

It is disapointing that the branching feature doesn't work with multiple repositories, particularly where a clean checkout is being done for each build (surely the common case?).

This widget could not be displayed.

I did something similar.

The first repo (default repo) I did the normal checkout. The second repo I used a script: 

${bamboo.capability.system.git.executable} clone -b ${bamboo.repository.git.branch} ${bamboo_repositoryUrl}

=> where repositoryUrl is a plan variable with the second repository url...

However now I ran into a new problem:

The trigger on the first repo works fine. But on the second repo it doesn't. If I check in on that repo on the default branch, all planBranches are triggered!  If I check in some code to a planBranch no build is triggered.

I have similar situation, so what i did was to create another plan that has no jobs in it. Configured the second repository with polling trigger for that new plan that has dependency against the old plan.

So the new plan will be triggered to the old plan whenever there is a changes in your second repository. You can also setup the new plan for the feature branch that will pass to the old plan for the respective branch to do the job too.

This widget could not be displayed.
Ben Stuart Atlassian Team Mar 12, 2018

Hey everyone, just an update on this. BAM-11544and BAM-14127 were released in Bamboo 6.3, There is also another feature request you may be interested in as well: BAM-19675.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

125 views 2 0
Join discussion

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