Using Bamboo 5.6, I setup a Linked Repository to Stash. However, it made me pick a branch. We have multiple release branches and I create 1 build plan PER release branch. However, I can't share the same linked repository in each of these build plans because the branch is hard coded to it. So I've had to add 1 linked repository for each different branch.
Is there a way to configure the branch used from a linked repository at the plan configuration level?
Is there a reason why you create a separate plan for each release branch? Have you considered using Plan Branches?
If for some reason Plan Branches are not an option (ie when release branches require different plan configuration) you can do the following:
Yes I originally had things setup that way but due to the inability to manually alter the bamboo build number per branch it was not sustainable based on our branching and release model. I'd go into more detail but it's not relevant to my question. I'd like to see an answer to my original question with regards to choosing a branch per plan using the same linked repository.
That really defeats the purpose of them IMHO. Their main role is to share repositories between plans but yet it forces the plan's branch to be what is linked in the repository. Just one more absolutely useless feature behavior in bamboo. Strange that it is the way it is when their other products make so much more sense.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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!
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