|
||||||||
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 |
- [JIRA] (JENKINS-15418) Git fails to clean w... jcarsi...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Git fails to cl... markewa...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Git fails to cl... jcarsi...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... jcarsi...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... onemanbuc...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... onemanbuc...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... jcarsi...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... onemanbuc...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... onemanbuc...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15418) Fails to clean ... scm_issue_l...@java.net (JIRA)
Hi,
Thanks for that interesting link.
You're right and we already worked on shortening our paths. We also wrote a few scripts which automatically map the current path on a new drive letter in order to reduce the risk to encounter that ridiculous Windows issue. But anything we do is only delaying the issue. And it came back with that job.
The point here is:
The deletion fails in Java File.delete() so there's no quick solution for that issue. But we could imagine some workarounds to reduce the times it's happening:
I can't see a "clean" solution but anything that could help to shorten the path when working on windows would help...