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

ENV variable to be used in task script argument

Dear Atlassian,


I have a custom variable

key: [executable.bamboo.test] value: [thisisatest] type: ENVIRONMENT

I want to use it in a deployment task as argument to a powershell script

-ConnectionURL ${executable.bamboo.test}


However, it looks it's not set yet or I used it wrong way.

What's interesting, if I dump all varialbles inside the script, I can see it's set.

Most probably I'm doing something wrong. It looks that ENV variable is not accessible to be used in scripts arguments. Other variables are fine, I mean global or build variables.

I appreciate you help. 

Kind Regards

1 answer

1 accepted

1 vote
Answer accepted

ok, guys, I finally realized that prefix bamboo is always required for variables.


Jimmy Seddon Community Leader Oct 29, 2019

Hi @zzzz,

I'm glad you were able to figure it out on your own! I was just logging in to tell you the same.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events