I am running version 6.3.1 of Bamboo. Reading the release notes for 6.3 it states that repository branches can be changed. I have 2 repositories setup in a plan. It seems only the default plan can be changed. The second repository can only be set to what ever is in the main plan. Is this correct? If I make the second repository the "default" or first in the plan list I still cannot change the branch in the plan branch settings. I also tried to setup a plan branch manually and I cannot change either repositorys' branch. The only select I have is "master"
Turns out this is a bug in bamboo. If you are using Username and Passwords to access your repositories and have more than one repository, the login credentials are not being passed properly for the non-primary repositories. Once i was able to upgrade my Bamboo license I was able to get support. There really should be a limited support window for Bamboo. For those who don;t have access to support this issue may not have been found out. Its kind of a big issue, at least to our use case.
Are you using linked repositories? If so you may be running into https://jira.atlassian.com/browse/BAM-16101.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Repo 1:
Repo 2 (You will notice I can only select the Dev branch. there are more branches than just Dev):
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's the problem, with our current license I can only write on the forums. Its kind of counter-productive since we sill paid money for it. I don't expect having access to a full support team, but allow one or 2 questions during this license period. For the most part Bamboo is rather easy to use and intuitive.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can anyone from the Atlassian team speak to this? The documentation does not seem to indicate that plan branching is limited to the default branch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I saw this post, but I wonder if the functionality has changed or if I have to perform a work around.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.