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

Is there way to chage specs varaible?

I am looking for a way to chage specs driven deplyment varaible.
I have a Java spec driven bamboo deployment plan, it contains bamboo variables, but since those variables are spec driven, I'm not allowed to change them using the UI.
So I'm looking for a way to create a variable that I can modify.

1 answer

I have found that once I'm using Specs to manage a build or deployment plan, I can no longer edit any of the contents of that build plan or deployment plan.

However, one thing you could try is, knowing that variables in a Deployment plan inherit the variables in the Build plan that it's based on.  If that build plan isn't managed by specs, you can create another variable in that build plan.  If your Build Plan is also managed by specs, the Build Project that contains the Build Plan can also have "Project Variables" that are ultimately inherited by the Build Plan, and thus the Deployment Project.  The downside is that you can't (without some kludge) have a Deployment Environment specific changeable variable in the Build Project variables.  For example, if there is a "deployment_target_host" variable that you define differently for each environment you deploy to, you'll have to do something like define the Build Project variable as "deployment_target_host_ENV1", "deployment_target_host_ENV2", etc, and then have some logic in the deployment environments that choose the "deployment_target_host" based on the names of the keys.  It's kind of kludgy, which means it's kind of fragile, but I guess it works.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events