Repository-stored Bamboo Specs and POM.XML

[vpogrebi]

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:

• IS POM.XML - AN ABSOLUTE REQUIREMENT FOR BUILDING BAMBOO PLANS FROM SPECS?

... or

• is POM.XML required only for LOCAL MAVEN RUNS, and something else needs to be done to enable REPOSITORY-STORED Bamboo spec builds without pom.xml?

[Chris Berry]

Hello Valeriy,

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.

Tutorial: Bamboo Java Specs stored in Bitbucket Server

thanks

Chris

Atlassian support- Bamboo