nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bamboo YAML import failed: Document structure is incorrect: Found following unused properties: plan-

Victorio Berra

Bamboo YAML import failed: Document structure is incorrect: Found following unused properties: plan-permissions

My YAML

---
version: 2
plan:
project-key: EEWTWS
  key: 'HEALTH2'  
  name: Health
plan-permissions:
  - groups: '_Bamboo__Build_Admins'
    permissions: admin

I dont understand what im doing wrong. I want _Bamboo__Build_Admins to be an admin on the plan when its created.

Accepted answers

Jack Nolddor [Sweet Bananas]

Hi Victorio,

Manage plan permissions to control which users have access to various functions of the build plan using Bamboo YAML was introduced in Bamboo v6.1.0.

Which Bamboo version are you currently running? Could be this the root couse of your problem?

Anyway, do you mind to try using the following content?

bamboo.yaml

---
version: 2
plan:  
project-key: EEWTWS
  key: HEALTH2
  name: Health

---
version: 2
plan:  
  key: EEWTWS-HEALTH2

plan-permissions:
 - groups: 
     - _Bamboo__Build_Admins
  permissions: 
     - admin

All comments

Jack Nolddor [Sweet Bananas]

Anyway, do you mind to try using the following content?

bamboo.yaml

---
version: 2
plan:  
project-key: EEWTWS
  key: HEALTH2
  name: Health

---
version: 2
plan:  
  key: EEWTWS-HEALTH2

plan-permissions:
 - groups: 
     - _Bamboo__Build_Admins
  permissions: 
     - admin

Victorio Berra

6.9.2 build 60911 - 04 Jul 19

Victorio Berra

Also im not alone. But his answer makes no sense. He probably doesnt even realize he disconnected the permissions from his plan by "moving them to a new block" whatever that means. Maybe we are looking at a real bug here?

Jack Nolddor [Sweet Bananas]

Hi Victorio,

I've added a YAML proposal in my original answer.
Not sure if it is the same as you are currently using since the YAML you post in the original post seems to be malformed (I believe because copy & paste here)

Alexander_kd9i5l

I'm fairly certain that plan permissions need to be in their own YAML document in order for Bamboo to use them, much like how build and deploy plans need to be separate from each other.

Ideally, it's best practice to keep your plans and permissions in their own file, and include them in your bamboo.yaml.

bamboo-specs
|-bamboo.yaml
|-build.yaml
|-permissions.yaml

bamboo.yaml:

---
!include 'build.yaml'
---
!include 'permissions.yaml'
...

build.yaml:

---
version: 2
plan:  
project-key: EEWTWS
  key: HEALTH2
  name: Health

I'm not quite sure how the permissions.yaml needs to be formed, but here's my guess at it:

permissions.yaml

---
version: 2
plan: "EEWTWS-HEALTH2"

plan-permissions:
  groups: "_Bamboo_Build_Admins"
  permissions: admin
...

The three dashes in a YAML file mark the start of a new YAML document.

Victorio Berra

My YAML all parses correctly but now I get a new error:

There was an error when processing yaml file "bamboo.yaml". File structure is correct, contact Atlassian Support for assistance on resolving this issue.

Could not parse key 'HEALTH2'
java.lang.IllegalArgumentException: Could not parse key 'HEALTH2'

I didnt change any of the details, I just created the new files and added the includes

Alexander_kd9i5l

Ah, try this in your permissions.yaml:

plan: "EEWTWS-HEALTH2"

I'll edit my above answer to put double quotes around that value as well.

Victorio Berra

What is the difference between double and single quotes in your YAML?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

spec