Is the stack trace in the bug description accurately describing the stack trace that you are seeing when checkout fails to complete on your Windows server? I assume it is. If it is not, then please place an accurate stack trace in the bug report for better diagnosis. If that stack trace is accurate, then there is a chance that a git process (either from Jenkins or elsewhere) has acquired a lock on the .git} directory inside the Jenkins workspace. That is not something I've ever seen before, but it is conceptually possible that another process might have a lock which causes the local git checkout to block while waiting for the lock to be released. Next time the problem occurs, use a command prompt window or a git bash Window on the agent where the workspace resides. Attempt to perform git operations (like `git ls-remote origin` and `git status` and `git log`) in that workspace while the Jenkins checkout is blocked. |