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

Does Bamboo Java spec have something like YAML's "!include"?

We are weighing Bamboo YAML against Bamboo Java specs.  We are looking for scalability features. There is a feature of YAML, "!include", that allows the inclusion of other files in the bamboo.yml file. This would help us manage a high volume of spec files.

Is there a similar feature in Bamboo Java Specs?

1 answer

That explains how to use !include in Yaml specs, but what I am asking is whether  I accomplish the same thing using the Java spec.  Since I am not a Java programmer, this may be a very naive question, but I am trying to figure out how to combine multiple build programs, connecting with different source code repos, in one Java Spec file.  

Oh, sorry I messed it up.

Regarding Java specs. First of all all files should be kept at same repo unless you want to deal with dependencies management using Maven\Artifactory.

In Java language you have concept of classes which are generally kept at different files and have access to each other.

So Java language is more scalable here, some of Atlassian teams use YAML Specs if they need to manage few plans, but if you need to manage 50+ plans then Java is more convenient tool. For example Jira dev team manages 4500+ plans at Java Specs.

After a few hours with a Java basics book, I was thinking that external classes would be a key.  Thanks for the confirmation. 

I would love a chance to learn more about how teams approach this.  When are separate plans used, when are edits applied to spec files for a core plan, etc.  Are you aware of any resources you could point us toward that discusses organizing and running a 50+ plan program using Java Specs?


I'm not aware of any external resources about organising of Specs code. Every team gradually evolves their codebase and follow approach which works best for them.

In Bamboo team we have combination of classes with plan config and utility classes for common operations like running test task, artifact definitions, docker images config etc.

In case others are looking I did find this article about one approach.

I am still struggling to completely understand it, but it is at least a pointer.

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 ...

240 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