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 votes
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.

There is a bugfix-update available for the Custom-Navigation-Plugin which resolves the issue above

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder

....sh :  #!/bin/bash source "$(dirname "$0")/common.sh" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables ROLLBAR_ACCESS_TOKEN...

177 views 0 11
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