|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
"Been there, done that"![]()
In my experience, disabling Windows Search and anti-virus merely reduces the problem, e.g. down from a 5% failure rate to a 0.5% failure rate.
On all my windows build slaves, I've configured Windows Search to only search the start-menu, then disabled the search service entirely, I've configured the anti-virus to exclude the Jenkins build area from its scans and on-access checking, and I was still seeing builds fail every week due to transient file-locking problems.
After implementing the fix for this (https://github.com/jenkinsci/jenkins/pull/1209) and applying it to my local Jenkins server, I haven't seen a single build fail due to these transient file-locking problems.