It is useful (vital for me) to tell the current branch of plan that is running. I used to use this variable: bamboo.repository.branch.name. But documentation says it is to be deprecated; and anyway, it does not always works. I mean, in some plans, it works fine, in others, it always contains value "master" no matter which branch is running, auto triggered or manually.
I also tried those variables:
But they always return "master" no matter which plan branch is running.
Why do I need to know what branch is running?
When the plan is triggered by a git commit, it should run with source code under the same git branch that contains this commit. It will not make sense, if a plan always run git branch master code, when commits are all happen under feature branches right? Also different branch can have different roles, like release branch will do deployment but other branch doesn't. In your plan config, you need do different things manually according to what branch is being run.
Does this make sense? What is the reliable way to get the current plan branch?
The variable bamboo.repository.branch.name is deprecated but the variables bellow (which you already cited) should do the same job.
Please keep in mind that those variables will depend on the repository type used and their order, where there is more than one. The <position> part should be changed accordingly to: 1 (for the first repository in the list), 2 (for the second), and so on).
Some questions that might help us moving forward:
I've run some tests with Bamboo 6.6.2 using Bitbucket repo and all my tests returned the branch as expected.
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
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