Upgraded to 3.2 path errors

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.

1 answer

This may be related to the Custom Navigation plugin, if you have that installed. See https://jira.atlassian.com/browse/STASH-5096 - is that what you are experiencing?

The initial migration will appear to work, but after a restart, Stash will fail to start up again.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

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&nbsp...

2,044 views 1 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you