We have upgraded to Stash 3.2 and during the upgrade we had several, but not all repositories not recieve the path change to /shared/data. They are still pointed at /data.
Where can I update this information in the database? Or what steps do I need to take to resovle the issue? We currently have put symlinks in place, but I would like to get a concrete solution in place.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot