Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

YAML Deployment Plan Permissions Error Edited

I'm having a problem similar to the one described in "Access denied : creating deployment project through Bamboo specs". Here's the link:

https://community.atlassian.com/t5/Bamboo-questions/Access-denied-creating-deployment-project-through-Bamboo-specs/qaq-p/784854

The solution described does not seem to work for me. I have tried deleting the deployment project, recreating it and configuring it's permissions as described, but the YAML specs in the Bitbucket repo, when scanned, continue to generate this error message:

The plan stored in repository 'Canary Deployment bamboo test' is not permitted to create new deployment projects
com.atlassian.bamboo.exception.UnauthorisedException: The plan stored in repository 'Canary Deployment bamboo test' is not permitted to create new deployment projects

And, on the Bamboo server side, I can see this error in the log:

2019-09-20 20:07:16,367 INFO [15-BAM::SpecsDetection:pool-22-thread-4] [RepositoryStoredSpecsServiceImpl] Bamboo YAML import failed

com.atlassian.bamboo.exception.UnauthorisedException: The plan stored in repository 'Canary Deployment bamboo test' is not permitted to create new deployment projects

I've verified that all the permissions are there. At least, all that I can find in the documentation. Any thoughts on what else I can try? Or if deployment plan YAML specs in a repo are supposed to be supported? 

Thanks

1 answer

1 accepted

0 votes
Answer accepted

Well, after looking at the problem for a long time, I realized the YAML deployment plan name was slightly different than the UI deployment plan name. That was what was causing the permissions error - the YAML spec was trying to create a deployment plan that did not already exist.

Everyone should note that the deployment: name: field in the YAML needs to EXACTLY match the deployment plan name displayed in the UI.

Thanks for sharing. I was about to share that I was able to make it work by adjusting the following permissions:

  • Specs repository >> Bamboo specs >> Access >> Access all projects
    This one is needed to allow project creation.
  • Specs repository >> Permissions >> Bamboo Specs repositories access
    This one is needed to allow the use of repositories that are referenced in the Plan and Deployment project.

I'm glad that you found what was causing the issue.

I am also facing same issue. But Bamboo append/perpend some characters after/before the name so in that case how i can use the same name and even i can't apply access to all projects because all projects not created by my team.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

595 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you