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

How to Use the Same Bamboo Deployment Project Structure for Different Deployments without Cloning

I would like to be able to use a single deployment project that can be initiated with different configurations (presumably with different variables) for different deployment needs. I don't want to take the baseline deployment project, clone it, and then use different variables for each cloned project. The problem with that is that if the structure changes, you have to maintain multiple cloned projects.

Here is a use case example I would like to be able to do:

deploymentA -> use baseline deployment project with deploymentA configuration.

deploymentB -> use baseline deployment project with deploymentB configuration.

deploymentC -> use baseline deployment project with deploymentC configuration.

etc. Any ideas are appreciated. Thanks

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events