Environment:Jenkins 1.509.4 running on Windows Server 2008 R2 64-bit, Git Client Plugin 1.6.0, Git Plugin 2.0
There seems to be a problem related to the core.symlinks config option. Usually, if core.symlinks is not set (the default), Git will probe the target file system for symlinks support when cloning (see ). As Windows does not support symlinks in the POSIX sense, Git for Windows internally uses core.symlinks=false if that option is otherwise unset. However, relying on this results in this error for me (see ):
Directly using Git from the command line on the server works fine to clone the repository, I do not get any errors about being unable to create symlinks then.
The error in Jenkins disappears when I explicitly do "git config --system core.symlinks false" on the build server (see ).