Problem
We've configured an environment, a pipeline and a step within that pipeline, but nothing happens when we try to trigger the pipeline platform is Windows 2008 R2. We have 3 build agents. The pipeline step is an MSBuild task.
Solution
Git checkout is a known issue on Windows when path length is too long for Windows to handle(ref: http://trac.openmicroscopy.org.uk/ome/ticket/4381).
Windows has a 260 char path limit on file-path length. To work around this change server installation to a shorter path like C:\go or increase file-path max-length limit (it seems there is a way to increase file-path length limit: http://msdn.microsoft.com/en-us/library/aa365247(v=vs.85).aspx#maxpath).
Git checkout fails on Windows when path length is too long
Comments
6 comments
You can use “Long Path Tool” !I have used it when i have faced same problem and it worked for me.
:)
Long Path tool can resolve error messages like: path too long, cannot delete file, too long path, destination path is too long, etc.
The Long path tool is the very best program for error, unlock solution.
Try it and solved your problem.
I used the long path tool and I solved my error, unlocks problem solution.
Long Path Tool is a software that will let you easily delete, copy or rename long path files.
Long Path Tool is one of the best tool to solve this problem easily....
Please sign in to leave a comment.