We are currently experiencing an issue on Bamboo spec files and we hope you can help.
The issue:
We have created a simple spec file, this spec file runs fine while it’s running from any branch. However, when we merge the specfile to develop (our default branch) it’s not being detected by bamboo anymore. When we scan for specfiles (under linked repositories) it tells the scan went okay but gives the following message:
“07-Jul-2022 04:39:34 Bamboo Specs haven't been found in repository 'repo name'. All plans managed by Bamboo Specs stored in this repository will be disabled. If you haven't deleted Bamboo Specs intentionally, make sure you have placed your Bamboo Specs in the bamboo-specs directory under the repository root.”
However, the file is there in bitbucket and when we check out our develop branch
If I change the linked repository branch back to my other branch the bamboo spec is imported. We have tried several things to resolve the issue but noting seems to work.
Some of the things we tried and observed are the following:
However, noting of the above seems to make any difference. We are highly depending on our develop branch so it is needed for us to get this to work.
Is there anything we can try to resolve this issue?
Regards,
Janus
MAKE SURE THAT BITBUCKET SERVER AND BAMBOO ARE CONNECTED USING APPLICATION LINK
Go to > Manage apps > Application links.
MAKE SURE THAT BAMBOO SPECS PROCESSING IS ENABLED IN BAMBOO
Go to > Security > Security settings. In the Repository Stored Specs security settings section select Enable Repository Stored Specs.
MAKE SURE THAT BAMBOO SPECS IS ENABLED FOR A REPOSITORY YOU PUSHED TO
Go to > Build resources > Linked repositories > <your repository>.
In the Bamboo Specs tab, enable Scan for Bamboo Specs.
MAKE SURE THAT BAMBOO SPECS HAS ACCESS TO PROJECTS OR DEPLOYMENT PROJECTS YOU WANT TO MODIFY
Go to > Build resources > Linked repositories.
Select your Bitbucket Server repository.
Select Enable all projects access or make sure that your build or deployments projects are listed in that section.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.