Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,456,634
Community Members
 
Community Events
176
Community Groups

Need a Single Definition for a Variable to be used by Deployment Environments w/i a Project

Running Bamboo 6.8.1

I understand the general concepts of variable inheritance:

  • Global
  • Plan
  • Build  (can be overridden w/ a manual build)
  • Release (takes snapshots of global and plan variables)
  • Deployment

My problem is that I have a single plan-level variable (password property) which needs to be evaluated at run time-time for a deployment. 

The release takes a snapshot of the plan variables (so if the value of my plan variable needs to change) the snapshot value in the release, which is stale / out of sync overrides it,

Yes, I know I can define a deployment environment variable -- but I have several deployment environments (11), so setting a variable value 11x vs once is not scalable for my project.

Basically looking for any *one* of the following:

  • ability to back reference a higher-level (overridden) variable
  • ability to reference a specified deployment variable from a specified environment  across different environments in the same project
  • ability to bulk set / define a core deployment-level variable across multiple deployment environments w/i a given project

Any suggestions would be appreciated.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events