I manage all my build plans (20+) in a single Stash Git repository 'Bamboo Plans', and had scripts to publish plans to Bamboo.
Since Bamboo in recent versions allows to do this on it's own, I'd like to migrate to this feature.
By trial & error I learned, that I have to create a "bamboo-specs" folder in that Git repository and put a pom.xml file there so that Bamboo sees the Bamboo Specs project.
Do I have to create one project _per_ build plan, or can I keep them all in one git repository (I would prefer this!).
Please help :-)
With Java Bamboo Specs it's totally fine to have a single repository which defines multiple plans and deployments for Bamboo. Furthermore, that's the concept Bamboo team uses internally to manage our plans.
YAML Bamboo Specs support only single plan - per repository at the moment.
Thanks Grzegorz for your reply.
I'm using Java Bamboo Specs, but Bamboo doesn't find my plans. The directory structure is like this:
I already moved everything under one bamboo-specs/ top-level directory, but without luck - Bamboo still doesn't see the plans.
Do you any other advise?
You should have only single Bamboo Specs project in bamboo-specs directory. Within this project you can have (and publish) as many plans as you want.
Please refer to the tutorial in order to get information how to create Specs project within your repository (there's a command you should use to get you started) and to the specs reference to get knowledge how to create and publish plans and/or deployments.
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 ...
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