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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Setting a variable that can be used by other build plans

Is there a way to set a bamboo variable like an artifact and then use this variable by another plan on some other date.

We have some docker images that we build out and I would like to store the docker image name that is set after that build (servicename:1.0.0.1).  Then on a down stream deploy of that image, I would like to get the docker image name from that variable and deploy it.

 

So essentially can we store a value in a bamboo variable that can be used later?

 

I know I could store the name in a file (lastimagename.txt) and then set that file as an artifact and pull that artifact and read the value out of the file but this is a long way to get to a variable that should be able to be set and used.

 

1 answer

0 votes

Hi @lance_lyons 

If I had to solve this problem with Bamboo I would try to set/get this information from the source code. This would assure that whenever an old build is a rerun or an old deploy is redeployed I would have the correct name used for that image.

We can't achieve that through Bamboo variables. You cannot set their values with the current implementation of Bamboo. You could use the inject variables but that would require the artifact to be set with the value (as you already know).

We have a feature that should cover the need you expressed:

Is it possible to add the content in the source code?
It could be a commit tag that will be set and read later. 
Does that make sense?

Suggest an answer

Log in or Sign up to answer
TAGS
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 ...

195 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