Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

YAML Bamboo Specs not creating Plan: Are there logs?

Alan Raison June 8, 2018

I've been trying to experiement with bamboo specs but no plans ever get created. I am use Bmaboo Server 6.5.0 build 60509.

I have successfully connected Bamboo with my Bitbucket Server (v5.5.0).

I have a linked repository containing a file `bamboo-specs/bamboo.yml`.

I have enabled the linked repository for spec-scanning.

I have created a project, whose key matches that declared in the YAML spec, and given the repo specs permission in that project. (I also tried giving the repo permissions in all projects).

Should the plans be automatically created at this point? I can't see any log lines to determine whether scanning has taken place, let alone been successful or otherwise.

I have tried clicking "Create -> Create Bamboo Specs" and choosing the project and linked repository. I see a message describing how to get started but then nothing changes - should I get feedback on the success of this?

There are no logs under the linked repository page's "spec status" tab.

I am not a Bitbucket admin, though I can get the admin to perform tasks on my behalf. The Bitbucket admin is an admin in Bamboo and was able to create the app link.

Have I followed the process correctly? Am I missing anything?

My spec file looks similar to this:

```yaml

project:

  key: BASE

  plan:

    key: MAVEN

    name: Custom Maven

stages:

  # Set up one Job per base image type

  - jobs:

    - scripts:

      - docker build \

        -f 3-jdk-8/Dockerfile \

        -t repo-address/maven:3-jdk-8-${bamboo_planKey}-${bamboo_buildNumber} \

        -t repo-address/maven:3-jdk-8 \

        .

```

*update*: sorry I see this has somehow got posted in the bitbucket section; will re-post in bamboo.

1 answer

1 accepted

0 votes
Answer accepted
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 8, 2018

Hi Alan,

Yes, it looks like you followed the process correctly. You can check in the logs (bamboo-home/logs/atlassian-bamboo.log) if the change detection event is arriving in Bamboo, you should be able to find something similar to the following log entry:

2018-06-08 20:40:29,818 INFO [http-nio-8085-exec-25] [AccessLogFilter] 172.18.0.4 POST http://bamboo:8085/rest/remote-event-consumer/latest/events/stash-branch-changed-remote-event 231809kb

If you want to increase the log verbosity to see details of the specs processing, you can add the below class to Cog>Overview>Log settings at DEBUG level:

com.atlassian.bamboo.configuration.external

Please remember that you need to commit some change in the bamboo.yaml file after setting up the linked repo and project permissions. 

Thank you.

best,
Gabriel Ribeiro

Alan Raison June 11, 2018

Thanks @Gabriel Ribeiro. It seems that the issue was with the Application Links. Although the Bamboo to Bitbucket link was successful, the reverse connection was not, although there was no indication in Bamboo. Once the link was fixed and I pushed a change to the repository my plans were created successfully.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events