|
||||||||
|
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/groups/opt_out.
File-locking is the bane of anyone running any kind of automated system on Windows, so I'd agree that this might well solve the problem, although you may find that what you actually want the Git plugin to do is to just delete the contents of the workspace, not the workspace folder itself, i.e. to call deleteContentsRecursive (which will give you an empty directory) instead of deleteRecursive (which will delete the folder itself).
I also got anti-virus stuff running on my build slaves (I've managed to keep them free from whole-disk-encryption), and despite that I've not noticed any builds fail due to file-locking issues since I started running a custom build of Jenkins LTS that has this fix in it.
I think that this amounts to a fair amount of circumstantial evidence that this fix works.