Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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 a Generic bamboo specs for all Plans/Projects


I would like to understand the possibilities of creating a generic bamboo spec using java that can be used by all the Plans/Projects. This spec would contain all the common tasks templated/parameterised and be used by passing variables according to the plan/project.

Any reference or suggestion around this topic would be helpful.

1 answer

0 votes
Jimmy Seddon Community Leader Dec 04, 2019

Hi @Immanuel J Daniel,

Welcome to the Community!

I did something similar to what you are talking about as a proof of concept for my company (we have since decided to move toward YAML specs instead).

Where I stated was I viewed/downloaded a copy of one of our plans as a reference point.  Then, I made three classes:

A publish class - which all it does is have a main method that creates instances of my "Build Plan" Class and publishes them to my Bamboo server

A utilities class - I made a second class that was simply a bunch of methods that would wrap the creating the various tasks I would need for all of my build plans so that I could use them as building blocks as needed, by passing in various pieces of required information and returning a object of the various task types. 

Multiple build plan classes - this contained members that would hold information unique to each build plan such as the name, the key and the linked repository, and I used that information to construct the strings that would be passed to the utilities methods to create the various tasks I wanted to use for the plan.

Now, I only every created one build plan class, but this setup allowed me to change the types of tasks that were being created based on what we needed the build plan to do.

I hope that helps as a starting point.


Suggest an answer

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

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

220 views 4 6
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