Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo plan labelling with overridden variable adds 2 labels instead of 1 label

I'm having one build plan with 2 branches: master and dev.

I keep software version in one of the plan variables: 

  • Variable name: MY_VERSION
  • Variable value: 1.0.0

I would like to label every build in master branch with "1.0.0".

In order to achieve it I created another plan variable:

  • Variable name: MY_BAMBOO_LABEL
  • Variable value: ${bamboo.MY_VERSION}

I managed to achieve it in my job configuration and it works fine:

Job -> Miscellaneous -> Labels -> ${bamboo.MY_BAMBOO_LABEL}


Now, I would like to override this value for every build from dev branch and label it with 1.0.0-SNAPSHOT. In order to achieve it I added a variable to the branch (not to the plan): 

  • Variable name: MY_BAMBOO_LABEL
  • Variable value: ${bamboo.MY_VERSION}-SNAPSHOT

Under the variable I get a little note that: 

Overrides plan value: ${bamboo.MY_VERSION} 


I was expecting to get only one label on builds on dev branch e.g.  1.0.0-SNAPSHOT however my builds are labeled with 2 labels, both 1.0.0 and 1.0.0-SNAPSHOT.

Screenshot 2019-10-01 at 10.15.25.png

What am I doing wrong? Is there another way to achieve it? 

1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 08, 2019

Hi @BartoszMiller

I've tried to reproduce this behavior without success. I'm running Bamboo 6.10.2 where the issue is not happening. 

  • Can you share the Bamboo version you are running so I can try this configuration again?
  • Are you rerunning the same build or running a new build?
  • Are you using any other configuration or plugin not mentioned that could affect this?

I'll wait for your comments.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events