-
Bug
-
Resolution: Unresolved
-
Major
-
None
The default behaviour of Jenkins is to empty a workspace and start all over, when the workingcopy is locked. In most cases an svn cleanup could solve the lock.
I'm working on a project where we have a 5.4 GB working copy, and our repo is litterally on the other side of the world. In such a case you don't want to do a new checkout (taking at least 2 hours), when "svn cleanup" would have been sufficient.
[JENKINS-9647] Try cleanup before emptying locked ws
Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Workflow | Original: JNJira [ 139821 ] | New: JNJira + In-Review [ 175163 ] |
Can you vote for this patch please: https://issues.jenkins-ci.org/browse/JENKINS-10169
My issue is also related to the whole modules getting deleted even if it is not really necessary. Thank you!