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,364,091
Community Members
 
Community Events
168
Community Groups

Bamboo Specs accessing code repository?

Edited

I'm working through a setup of Bamboo Specs. Due to firewall restrictions I'm unable to host my bamboo specs repo out in the cloud since it wouldn't have access to my internal Bamboo server; as a result, I've also installed Bitbucket Server on the same machine running Bamboo and have linked these two apps on this machine.   This Bitbucket server instance is only to store my Bamboo Specs changes. 

Using the "Bamboo Specs tutorial" I can push changes to this tutorial's plan and all works as expected.  Obviously, this tutorial plan has not repos defined.

I'm having problems when I try to change one of my real build plans, where the source for the plan is a linked repo out on Bitbucket Cloud.  The changes are clearly noticed by Bamboo but I end up with the following error:

repository '(Bamboo Server's bamboo-specs repo)' is not permitted to use following repository(ies): (Bitbucket Cloud repo used during build time)

com.atlassian.bamboo.exception.RssPermissionException: The plan stored in repository '(bamboo specs repo)' is not permitted to use following repository(ies)...

 

How can I get Bamboo to simply process my Specs changes and not have it do anything with the linked repo in the cloud?  

I've tried adding my Specs repo to this plan as the first entry (the "default"?) hoping it would just "use" (whatever that means; unsure what it's trying to do) the repo running on my local Bitbucket Server.  

How can I work around this error?

thanks

1 answer

1 accepted

2 votes
Answer accepted

Hi @Kevin Matlock

The issue you are facing seems to be caused by a missing permission configuration in your linked specs repository.

Do you mind checking if the specs linked repo has the Repository configuration >> Permissions >> Bamboo Specs repositories access configured as expected for the repositories that your plan is trying to use?

Excellent, this addressed the issue.  I didn't see much documenting the need for that, but this was certainly my problem.

Thanks very much for the response and for the help!

Hi @Kevin Matlock

Thank you for the feedback. I've opened the following feature request to address this issue. Voting on it is a good way to flag this as something important.

Have a good one!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events