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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,456,745
Community Members
 
Community Events
176
Community Groups

Access denied : creating deployment project through Bamboo specs

Hi,

I am trying to Create a deployment project through bamboo specs .I am facing an error stating that my bamboo specs doesn't have authorization to create deployment project . What permissions should I provide for bamboo specs repository ? I can create & edit build plan and edit deployment plans but cannot create deployment project .

Thanks,

Naveen

2 answers

Hi @sudip saha ,

The Bamboo Specs linked repository needs to be linked to the project.

Navigate to your project settings, and select "Bamboo Specs repositories" in the "Security" section on the left side of the screen. From there, add the linked repository to the list of repositories.

You should now be able to re-scan the linked repository where the Specs are stored, and it will publish as long as there are no compilation errors.

 

Cheers

If you need to allow creation of deployment projects from Bamboo Specs you should grant All projects permission at Bamboo Specs tab of repository. Same tab you used to enable Bamboo Specs for that repo.

We cannot provide access to all Projects for a Bamboo specs repository because each project has its own specs and it is not allowed to access other project's . Is there any alternative ?

Create deployment project manually and then manage it via Bamboo Specs

Thanks for the reply Alexey . We are currently manually creating deployment project and providing authorization to Bamboo Specs . It's kind of hectic to create manually every time  and thus looking to see if it can be created automatically and what access is required for it . Is providing access to all projects is the only way for it ?

Thanks,

Naveen

If you want to create deployment project from Bamboo Specs code in repository, then yes - it's the only way.

Hi  @Alexey Chystoprudov. after your suggestion above we have:

1) Created manually a Deployment project linked to a repository

2) Generated the Deployment Specs using the View project as Java Specs option

2) Uploaded it to the linked repository

 

We expected this way to be able to modify the Specs without needing to grant All projects permission at the Bamboo Specs tab.

Unfortunately, we still get the UnauthorisedException below:

 

com.atlassian.bamboo.exception.UnauthorisedException: The plan stored in repository 'XXX' is not permitted to modify the deployment project 'YYY'

01-Jan-1970 01:00:00             at com.atlassian.bamboo.configuration.external.DeploymentImportServiceImpl.lambda$importDeploymentPermissions$1(DeploymentImportServiceImpl.java:272)

01-Jan-1970 01:00:00             at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)

 

Any idea why?

Hi @sudip saha ,

The Bamboo Specs linked repository needs to be linked to the project.

Navigate to your project settings, and select "Bamboo Specs repositories" in the "Security" section on the left side of the screen. From there, add the linked repository to the list of repositories.

You should now be able to re-scan the linked repository where the Specs are stored, and it will publish as long as there are no compilation errors.

 

Cheers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events