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

0 vote
Adam Ahmed Atlassian Team Aug 10, 2014

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jun 12, 2018 in Bitbucket

Do you use any Atlassian products for your personal projects?

After spinning my wheels trying to get organized enough to write a book for National Novel Writing Month (NaNoWriMo) I took my affinity for Atlassian products from my work life and decided to tr...

25,469 views 26 12
Join discussion

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