Mark Waite edited a comment on Bug JENKINS-18951

As a specific test of the msysgit core.longpaths setting, I used the git repository https://github.com/MarkEWaite/longpaths.git with 4 branches

  • master - a 64 character directory + file1
  • branch-128 - a 128 character directory + file2
  • branch-192 - a 192 character directory + file3
  • branch-256 - a 256 character directory + file4

I defined the job to use the default git implementation, only execute on windows, and to execute a windows batch command:

git config --add core.longpaths true
dir /s 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef

I defined the job to use */branch-128 then ran it. The console log showed the recursive directory as expected.

I defined the job to use */branch-192 then ran it. The console log showed the recursive directory as expected.

I defined the job to use */branch-256 then ran it. The console log shows the recursive directory through the third level, then the DOS command prompt reports "directory name too long" for the 256 character directory name.

It is important that the workspace is not "wiped" between those changes to job definition. If you "wipe" the workspace then run the job with branch-256 as the checkout branch, the job will fail because the local change to the core.longpaths value is not made until after the repository is cloned and the branch checkout is complete.

In case it is helpful, a deeper description of the problem is available at http://osdir.com/ml/msysgit/2014-02/msg00062.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to