I have bamboo linked to stash. I have several linked repositories. Occasionally and for no apparent reason I get the following error.
This happensd on different repositories at different times. Saving the repository configuration works.
What are the possible causes of these errors? Why are they random and what to do about them?
We noticed this when either Stash, or JIRA for whatever reason crashed unexpectedly. Even though we would save the details again is the error message suggested, the only way to resolve this error was to restart the Bamboo instance.
Even though we were adding new linked repos (and plan specific repos) the error would still appear there. As such we were left with no other choice but to restart the entire instance of Bamboo.
This answer may or may not help you, but you definitely aren't alone in seeing this symptom.
For Stash type linked repository, a key pair is generated and added to the Stash user profile of the user adding it. This means that the permission for the repository is based on the user.
Normally this could happen if access is removed or the user deleted completely. Saving it again in linked repository regenerates the key and readds it to the new user profile who saved it.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot