You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.