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

Defining environment variables

Hello - I want to define an environment variable in bamboo so that certain tasks are completed during execution. How do I do this through the web interface? bamboo_run script is looking for the value of this variable and I want to set it to true instead of false so that it performs the task from within bamboo. 

1 answer

0 votes
Eduardo Alvarenga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 14, 2022

Hello @Karen West

Welcome to Atlassian Community!

In your Plan configuration, you can use a Script Task or any other task that would create a variables file, then add an Inject Variables task that would consume that file.

The Inject Bamboo variables task allows you to read the values for variables from a file, and create those variables in your build plan.

The file should use a 'key=value' format. Note that starting from Bamboo version 5.14, you must provide relative paths to the property file.

You can choose if those variables should have a local scope (in which case they cease to exist when the job finishes) or result scope (in which case they are persisted and passed into subsequent stages or related deployment releases).

Then, after the variables are set you can configure a Conditional Task to evaluate the new variable and then proceed with its execution in case it matches.

Thank you,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

Thank you Eduardo. I will try that tomorrow and let you know if it solved my issue.

Cheers - Karen West

Like Eduardo Alvarenga likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events