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

Set variable value at runtime

For my deployment I would like to be able to set the container tag at runtime. For example. 

I have 2 containers:




I have a manually triggered deployment step.  I would like to be able to do something like this in my code:

- helm install ${container_name}_chart --version=${container-version} --set cotainer_tag=${container_version}

Where container_name and container_version are set by the user at runtime. 


At runtime the user can enter (or even better, if possible select from a list) the container/app name and version.


Is this possible?


1 answer

1 accepted

0 votes
Answer accepted

Hi @Eytan Yammer,

It is possible to set variable values at runtime but only for custom builds and for variables defined in these builds.

You can see an example in the following doc, if you search for the keyword 'variables':

Since this step is manually triggered anyway, you can define it as a custom pipeline instead, and define container_name and container_version as variables in that custom pipeline. I'm afraid it is not possible to select values from a list, the user running the step will need to provide the values for these variables.

It is also possible to use the 'deployment' keyword for this step in a custom pipeline if you are making use of deployment environments in Pipelines.

Is this something that works for you?

Kind regards,

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events