You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
Thanks for looking at this post. I am working on a use case where i have various build/deployment plans and many environments already created manually from the front end and i want to use Bamboo spec to dynamicaly add a new environment to all the deployment plans in the system. I am able to create a deployment plan using existing plan key etc but in the case of exisiting deployment plans if i just put the new Environment object in environments() method it deletes the existing environments. I can add all the existing environment object along with the new Environment object in environments() on Deployment Object but i believe it just replaces and recreates the existing environments which i dont want as i am not sure it retains the history for existing ones. Idealy i dont want to touch existing environments at all as PROD is one of them. Any Help would be great.
Thanks,
K Sat
Hi,
As long as environment in Bamboo and in Specs match, the existing environment will not be removed, only updated, with all the history retained.
You can use 'View as Java Specs' option in deployment configuration to get the code for all existing environments. Just copy-paste it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.