Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Creating and maintaining multiple deployment environments in Bamboo


Hi, I am new to Bamboo and have the following problem: I have created a deployment plan and need to create multiple environments (probable dozens). What bothers me is that tasks can only be defined at the environment level and not at the plan level. So I need to create to recreate every task again and again for each environment. This is a lot of work and likely to produced errors. I don't think I am the first one to experience this. Is there a smarter way to do this?



2 answers

1 accepted

0 votes
Answer accepted

I didn't get it working at all. So I removed my Java Specs files from my project. I resorted back to creating everything manually.

So you suggest, I create a program that during the build creates and updates the deployment plan and environments?

You can run it manually, in an automated build, or you can use _repository stored specs_:


The point is: if you want to maintain a big number of plans or deployments in Bamboo, Bamboo Specs is the way.

Thank you Marcin. I will need some time to plow through the documentation in order to adapt.

I tried to read the documentation, but it is really confusing. Is there a possible way to export my current project/plans, edit, at them to source control, and automatically recreate and update them?

I have exported my deployment plan into Java specs. What disturbs me is the almost the whole plan compacted into one big statement on multiple lines. This makes it very hard to add loops, conditions, etc. The same goes for the documentation. It makes me wonder...

I cannot get my build and deployment plans to create or update. I have read and followed the instructions on the following pages and others:

Before you begin:
JDK 8 or higher: Yes on the build server, Java is 8.14 and Java SE Development Kit is 8.92
Maven 3.2 or higher: Yes, Maven 3.5.0 on the build server
Eclipse or IntelliJ IDEA IDE: no, I use Visual Studio locally.
Bamboo 6.0 or higher: Yes, Bamboo 6.4.1 on the build server.

Step 1: Create a project base with Maven: Skipped. I already have a project.

Step 2: Import the project into IDE: Skipped. I already have a project in source control, and that works fine.

Step 3: Define a job with a script task: I have exported my deployment plan and saved it to I have already made changes to it, since the way the exported code is unmaintainable.

Step 4: Validate Bamboo Specs offline: I ran 'mvn.cmd test' in the build directory and nothing happened. So the test is OK allright?

Step 5: Publish Bamboo Specs to the Bamboo server: code is commited to BitBucket and the commit comments are visible in the buildscreen.

Step 6: Check the results: nothing happens

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo Data Center on Kubernetes

Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...

66 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you