Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

190 views 4 6
Read article

Community Events

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

Events near you