-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows
I am using a SVN repository which is being checked out at the beginning of every build in a Jenkins job. It is set to "poll SCM" for updates. However, regardless of whether there were changes or not it is cleaning out the workspace and downloading the whole repository in it's entirety every time which is unnecessary.
Builds are taking much longer than they should as the SVN poll should only be checking out newly-updated files. Sample log:
Checking out a fresh workspace because the workspace is not file://PICKLE/Repositories/project
Cleaning workspace.....
- is duplicated by
-
JENKINS-13913 after upgrading Subversion Plugin to 1.40 some (not all) project are building again and again
-
- Open
-
I found one way to reproduce this: if I check out more than one path and I don't specify a target directory, it appears that the subsequent check-outs corrupt the files in the .svn subdirectory. Specifying a different target for each make it work correctly.
I also googled and found an example where the user used different capitalization for the host name than was stored in the .svn, and had the same effect.
Hope this helps!