Bamboo variable for branch name

With the new branch support in Bamboo 4.1 a plan can have multiple branches. Looking at https://confluence.atlassian.com/display/BAMBOO/Using+global%2C+plan+or+build-specific+variables however it seems there is no variable that contains the branch name.

Is there a way to access the branch name via variables? I am using the Tomcat Deploy Taks and would like to deploy the application to a different application context depending on the branch name.

7 answers

1 accepted

I think there is no one-for-all variable to access the branch name in 4.1 - I think that feature is scheduled for 4.2, but I'm not 100% sure.

However, if you're using for example GitRepository (as your default repository in Bamboo plan), then I think you could utilize GitRepository-specific variable for branch:

https://github.com/atlassian/bamboo-git-plugin/blob/master/src/main/java/com/atlassian/bamboo/plugins/git/GitRepository.java#L709

What repository type are you using?

Cool thanks, ${bamboo.repository.git.branch} works fine though it doesn't seem to be documented.

I'm trying to use this ${bamboo.repository.git.branch} variable in 4.0, but it doesn't seem to work. Are my findings accurate?

I'm trying to use this ${bamboo.repository.git.branch} variable in 4.0, but it doesn't seem to work. Are my findings accurate?

Looking at the Artifacts path, bamboo is putting the wars inside $plankey-$planX-$buildNumber

where X looks like the branch number (but not id, just integer counting from 0). Is that correct?

Do branches have their own Plan Key ? or anything else that can be pulled from Bamboo to distinct which branch is being built inside maven pom file?

Hi Radoslaw,

You are right that Bamboo creates new directory for each Bamboo branch and adds an integer to the name starting from 0. However, the best way would be using ${bamboo.repository.git.branch} variable. I tried it in Bamboo version 4.2, and it worked just fine. I have created a new task (https://jira.atlassian.com/browse/BAM-12129) to update the documentation (https://confluence.atlassian.com/display/BAMBOO/Using+global%2C+plan+or+build-specific+variables). If you are using an older version, try to upgrade your Bamboo instance as there are also many improvements and bug fixed in 4.2 related to Bamboo branches.

Cheers,
Armen

Everything would be perfect, but I am using SVN not GIT :-) Will the same bamboo.repository.svn.branch work?

The configuration of checking out from SVN repository is different (you just use the branch name in the URL: http://blog.evanweaver.com/2007/08/15/svn-branching-best-practices-in-practice/) from that for Git, and the plan branching feature is not implemented for SVN yet. You can work around it by defining a custom plan variable and use that to get the SVN branch name in your tasks.

Cheers,
Armen

Radoslaw,

You are right, my bad. I found this improvement request (https://jira.atlassian.com/browse/BAM-11660) that was implemented in 4.2.

Please let me know if you have any further questions or concerns.

Cheers,
Armen

Thanks for the info , I am trying to add this ${bamboo.repository.git.branch} in notificationCommontext.ftl . But not working, Can you guys please guide me where to add this variable ?

I want to see branch name in thw notification header in the email. Is it possible in bamboo ?

Thanks in advance

Hello Latha,

Hm... I think this is quite different use-case - Bamboo variables aren't auto-expanded in the notification ftls. I think you should raise your problem as a separate question on answers.atlassian.com - here it might become lost.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

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...

1,324 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you