Bamboo Github branches only show 30 branches and do not load in all branches

[lance_lyons]

We are using Bamboo 5.6.1 build 4410 and have noticed that the repository configuration using github only bring in 30 branches and do not show the branches that we are needing to build from.

Our product license is valid but we are out of maintenance.   Is there some form of work around that allows us see all of our branches?

[lance_lyons]

I typically dont like to go into SQL and make the change but I did find that you can alter the XML_DEFINITION_DATA in the dbo.VCS_Location table and set the branch that you need as a work around.

Stop Bamboo

Backup bamboo db

update the xml_definition_data column for the repository being used.

    <github>

      <username>OurUserName</username>

      <password>jEncryptedPassword</password>

      <repository>Github Repo</repository>

      <branch>branch name</branch>

      <useShallowClones>true</useShallowClones>

      <useSubmodules>false</useSubmodules>

      <commandTimeout>180</commandTimeout>

      <verbose>

        <logs>false</logs>

      </verbose>

      <fetch>

        <whole>

          <repository>false</repository>

        </whole>

      </fetch>

    </github>

restart bamboo and check.

[Steffen Opel _Utoolity_]

This has been a long standing issue that has finally been addressed in Bamboo 5.10.0:

• https://jira.atlassian.com/browse/BAM-15686
• https://jira.atlassian.com/browse/BAM-14542

To receive the fix, you'd need to update Bamboo accordingly, which implies that you need to renew your Bamboo license so that you are eligible for maintenance

Workarounds

Both aforementioned issues feature (somewhat quirky) workarounds provided by affected users, for example:

Here is a workaround: right click the select box and going to inspect element. Where it shows all the <option>branch</option> just rename one of the "branch" fields with your desired branch and hit enter. Then without refreshing the page select that option and save.

[Alexey Chystoprudov]

It was fixed in 5.10.0 - https://jira.atlassian.com/browse/BAM-15686