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
6.2 release of Bamboo brought possibility of storing build plan configuration (Bamboo Specs) in Bitbucket repository (https://confluence.atlassian.com/bamboo/bamboo-6-2-release-notes-938641951.html). Bamboo documentation describing enabling this feature (https://confluence.atlassian.com/bamboo/enabling-repository-stored-bamboo-specs-938641941.html) provides step-by-step instructions on how this can be done, but mentions nothing about any additional dependencies or requirements to make it actually work.
When our team tested this functionality (by downloading Bamboo specs from existing plans, storing them in Bitbucket repo, and then creating a test project that uses that Linked Repository) - demonstrates that when repo contains nothing but the plans themselves (*.java specs) updates to the repo result in NO PROCESSING (Bamboo logs generated in response to repo updates - are entirely blank, containing nothing).
Our subsequent tests demonstrated that pom.xml is required to start the build process...
So questions are:
Repository-stored Bamboo specs will look for bamboo.yml if the repository root or the bamboo-specs directory. If found it will use the YAML specs definition.
If no YAML definition is found it will look for a maven project under the bamboo-specs directory and use Maven to build the Java specs definition. Maven requires a pom.xml.
Atlassian support- Bamboo