Is there a way to set the default branch in Bamboo that is NOT "master". I want to set it to the default feature branch that we're working on. We encounter issues when building sometimes building Master by accident instead of the expected feature branch. How do we change the default branch?
You can change this on the Linked Repository if you want the default to always be the feature branch, we actually don't release from master so I rarely have that set in the linked repo:
If you want this to be more of a temporary thing while you are working on the feature branch you may want to consider using Plan Branches, which will create a "copy" of the main build plan that is linked to it but it only builds a given feature branch. You can find out more information about those here:
I hope that helps!
Hi James - I actually want a bit of both.
I read through the docs you provided on your second answer and it did not assist me in what I require.
When I changed the "default branch" in BitBucket it did not reflect in "Bamboo". So when I click on the app the default branch that appeared on the page was still "Master". Whilst it did work on BitBucket - I want it to actually work in Bamboo
I want to continuously change the default branch so that everytime I go to build the branch that appears on this section here is ALWAYS the current feature branch we are working on.
I should have clarified, the first screenshot I provided is actually from within Bamboo. If you go to the Administration cog and select "Linked Repositories". This will bring you to a listing of all BitBucket repositories you have linked in Bamboo. Then select the repository that you which to change the default branch for and my screenshot should make sense from there.
If you change the branch from within Bamboo, that should change the main branch that the build plan is built with,
I hope that helps!
Hi James - thanks for the clarification and the follow up much appreciated!!
Unfortunately we're working with many applications so I'm worried this would interfere with other plans. As the "Linked Repositories" state:
"Repositories defined here are available to every plan. You can select these repositories in plans configuration. Changes to them will be applied to every plan that uses them."
The section I've highlighted worries me as I'm not aware of whether or not this will interfere with other projects using the same Bamboo.
So you have two options here:
1) You can create a new linked repository that uses a different name but links to the same repo and uses a different default branch (I have done this myself for the exact reason you have listed above)
2) You can check the "Usages" Tab on the linked repository to see all the Build Plans and Deployment Environments that reference/make use of that linked repository:
I hope that gets you what you are looking for.
** SOLUTION **
Hi James wow sorry i thought I replied to this with my solution. So I was actually able to solve this by doing the following if you refer to the screen shot below. It's been working fine since the noticeable differents are the feature branches have changed naming convention in Bamboo.
They now have feature/2.0 <-- with the`/` character rather than the `-` character. Also I have encountered different issues running it with this "default branch" that is triggering other branches but I believe that is project specific - still investigating however not affecting my desired result.
I really appreciate your help James! Thank you kind sir!
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events