Important note: If you cloned linked repositories in the past because of this limitation and you use Plan branches, please watch out for this bug: BAM-20061

Long story short: you no longer need to create new linked repositories when you want to build branches in new plans. However, please proceed with caution when getting rid of such repositories created in the past.

The bug is currently on our short term roadmap .

Hello,

Since Bamboo 6.10 there's a new feature in repository configuration that does exactly that:

Hi Atlassian team,

in Bamboo version 6.10.3 I am seeing an "Override branch of a linked repository" option in our plan repository configuration. And as far as I can tell this is exactly doing what this ticket here is asking for, am I right?

Would be great if you could confirm and resolve this ticket here accordingly so that others are informed of the new feature.

As I said, we are currently on a 6.10.3, we upgraded recently from a 6.4.1 and if I remember correctly the 6.4.1 did not have this option yet.

Cheers,

Marco.

I think that BAM-18090 requires additional settings to be overridden, which would be totally fine with me

I also noticed that in my first comment I meant to write this instead of what is written there:

In Bamboo a repository is always a "Git repository reduced to a specific branch".

(the position of the quotes was wrong)

Another way to put this: A repository in Bamboo is a branch of a git repository. This makes it quite imho quite obvious that the current implementation makes not so much sense.

Also I believe BAM-18090 a duplicate of this issue.

Would be really great to have this. Here’s our use case: We use different main branches for different products built from the same repository, and currently we have to manually set up a repository for each plan in Bamboo in order to be able to have different master branches for each plan. Being able to use a linked repository and just override the master branch for a specific plan would make this much easier.

I believe this request would make a lot of sense. In Git a repository is a collection of different branches. In Bamboo a repository is always a "Git Repository" reduced to a specific branch. As far as I can tell the same situation applies to other Source Control systems.

Thus it seems to be very natural to define a repository and simply select a Branch for a given Build Plan. Plan Branches are not really an option since those are meant for things like Feature Branches and not Branches that have little or no relation. In my case I have Branches for different Versions and the corresponding build plans evolve over time which also means that Plan Branches are not an option.