Hi,

we have set up our Bitbucket Server installation to use a network share on one of our storage servers to store the contents of BITBUCKET_HOME.

The BITBUCKET_HOME env-var on the Bitbucket server looks like follows:

\\net_share\Repositories\stash_home

Everything works fine, except when we try to create a fork of one of our repositories, then we get the following error from git that is reported through the Bitbucket UI:

'C:\Program Files\Git\cmd\git.exe clone --bare --shared \\net_share\Repositories\stash_home\shared\data\repositories\23 \\net_share\Repositories\stash_home\shared\data\repositories\62' exited with code 128 saying: Cloning into bare repository '\\net_share\Repositories\stash_home\shared\data\repositories\62'... fatal: '\net_share\Repositories\stash_home\shared\data\repositories\23' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

The interesting part for this bug is that git tries to access the net-share with only one leading backslash ... \net_share
I think GIT needs some different formatting of the path to the network share to make it work correctly.

Thanks