Make sure you pushed your code to the Bitbucket Server

It's trivial but it really happens.

Make sure that Bitbucket Server and Bamboo are connected using application link

1. Go to   >  Application links

Make sure that Bamboo Specs processing is enabled in Bamboo 

1. Go to > Security settings > Repository Stored Specs security settings > Enable Repository Stored Specs

Make sure that Bamboo Specs is enabled for a repository you pushed to

1. Go to > Linked repositories > <your repository>
2. In the Bamboo Specs tab, enable Scan for Bamboo Specs.

Make sure that Bamboo Specs has access to projects or deployment projects you want to modify

1. Go to Administration > Linked repositories.
2. Select your Bitbucket Server repository.
3. Select Enable all projects access or make sure that your build or deployments projects are listed in that section. See Enabling repository-stored Bamboo Specs.

In case compilation fails during the first execution of Bamboo Specs, no plans or deployment projects are created or updated. As a consequence, Bamboo is unable to associate the Bamboo Specs with any plan, so you will not find an error log in any of the existing plans.

In case compilation fails not at first time, you can find "Specs execution error" on the build results page for the related plans.

Note that in both cases a committer of the change will receive an email with details of the error.

 
Compilation may fail due to two reasons:

• errors in the source code
  
  Check out the repository on your computer and build it yourself ("mvn compile" or import into IDE) to locate the error. These are usually code typos, wrong project dependencies or an outdated parent pom version.

• pom.xml has been sanitized by Bamboo
  
  By default Bamboo Specs are executed with a default pom.xml film, i.e. it will not use pom.xml from your bamboo-specs project. For that reason, even if your bamboo-specs project compiles and runs correctly on your computer, it may fail in Bamboo. Make sure that:
  • it's sufficient to compile your project using maven-resources-plugin and maven-compiler-plugin only instead of using for instance extra plugins for code generation; don't rely on executing tests

  • it's sufficient to compile your project with bamboo-specs and bamboo-specs-api dependencies only - don't add extra dependencies

  • your pom.xml inherits from com.atlassian.bamboo:bamboo-specs-parent 

Repository-stored Bamboo Specs feature requires your project in the/bamboo-specs directory will consist of only one Maven module. We do not support multi-module builds. So in case you put some Bamboo Specs classes in sub-modules of bamboo-specs, they simply won't be built.

Committer of the change will receive an email with details of the error. You can also look up for "Specs execution error" on the build results page of the related plan(s). Most typical reasons are:

Insufficient permissions

Make sure that Bamboo Specs has access to projects or deployment projects you want to modify. It applies also to dependent projects, for instance:

• child plans triggered after a build - see plan's dependencies section, 
• artifacts downloaded from a plan from another project.

Validation errors

Bamboo validates your plan configuration for correctness. It reports an error if any constraint is violated, such as: invalid project key, reference to non-existing repository or plan etc.

1. Go to <Coghweel> Linked repositories.
2. Select your repository.
3. Click on the Bamboo Specs tab.
4. Copy the webhook URL.
5. In therepositoryyou want to use for storying Bamboo Specs, go to your repository settings. 
6. Find webhook-specific configuration. 

7. Paste in the URL Bamboo provided you with.

1. In the top navigation bar, click Projects. 
2. Select your project. 
3. Click Project settings > Bamboo Specs repositories. 
4. Select your repository and click Add.
5. Go to settings the repository you want to use for storying Bamboo Specs.
6. Find webhook-specific configuration. 

7. Paste in the URL Bamboo provided you with.

Make sure that Docker is running. Alternatively, disable Bamboo Specs processing in Docker security settings, see Repository-stored Bamboo Specs security.