I got our networked storage for Stash set up finally. I copied the stash-home directory to the new location, updated the environment variable and started the server. However, whenever Stash tries to enter a git command there is an error message
"C:\Program Files (x86)\Git\cmd\git.exe" clone --bare -
-shared \\drive\stash\stash-home\data\repositories\24 \\drive\stash\stas
Cloning into bare repository '\\drive\stash\stash-home\data\repositories\51'
fatal: '\drive\stash\stash-home\data\repositories\24' does not appear to be
a git repository
fatal: Could not read from remote repository.
I logged into the machine, and found that
>git clone \\drive\stash\stash-home\data\repositories\24
has that error message but
>git clone //drive/stash/stash-home/data/repositories/24
works perfectly. I tried setting the STASH_HOME variable to both //drive/stash/stash-home and \\drive\stash\stash-home, but both options seemed to work the same. How could I overcome this so that the git repos are on our backed up storage?
Unfortunately, if Stash is running non-interactively as a service, mapping a network drive is not an option.
As it turns out, there is a relatively simple workaround for this. Use the mklink command to create a symbolic link to the networked location, and then point Stash at the symlink.
If you set up a UNC path for our STASH_HOME directory (e.g. \\myfileserver\sourcecode) you will have issues. You should change it to a mapped network drive instead you will avoid issues.
Please use this Knowledge Base article as a referrence:
Please also observe the length of the path might cause you issues.
I hope this helps you.
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