Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,369,281
Community Members
 
Community Events
168
Community Groups

Yaml specs version 1 -> version2

Hi,

How is it possible yo upgrade the yaml specs for a project in Bamboo.

I've upgraded the yaml specs, but I get the following error message when the specs are parsed:

Bamboo YAML import failed: Plan with name: 'PD-Build' already exists in project 'PD'. Can't create a new one with same name.

Do you need help? Please visit the http://docs.atlassian.com/bamboo/docs-0609/Bamboo+Specs+troubleshooting page.

I would like to keep the build history of the old plan

Regards,

Aske

2 answers

1 accepted

0 votes
Answer accepted

It should be 

---
version: 2
plan:
project-key: PD
name: PD Build
key: BUILD

Yeah - I messed up in the version 1 yaml spec with two keys, used the wrong one...

Thanks

0 votes

Hi @Aske Jenstrup Olsson 

 

Are you importing a new "plan" via v2 instead of updating the existing v1 spec?

I was just updating the bamboo.yaml specs to version 2:

from:

project:
key: PD
plan:
key: PD-BUILD
name: PD Build
key: BUILD

stages:
- jobs:
- scripts:
- '#!/bin/bash'
- './gradlew clean build'
testParsers:
- type: junit
testResults: '**/build/test-results/**/*.xml'

to:

---
version: 2
plan:
project-key: PD
name: PD Build
key: PD-BUILD

stages:
- Build:
jobs:
- Build

Build:
tasks:
- script: |
#!/bin/bash
if [ -f bamboo-specs/ci_build.sh ]; then
chmod +x bamboo-specs/ci_build.sh
./bamboo-specs/ci_build.sh || exit 1
else
./gradlew clean build
fi
- test-parser:
type: junit
test-results: '**/build/test-results/**/*.xml'
Like Lenin Raj Rajasekaran likes this

Hm, while replying I see there are 2 keys in plan section of the original yaml spec. Maybe that is the issue.

-Aske

Like Lenin Raj Rajasekaran likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events