Jenkins 2.x + svn plugin 2.5.7 glitch : directory is not a working copy (E155007)

[Warren Postma]

I have seen this problem many times since early Jenkins+svnkit 1.x days.   Typically a big 10 gigabyte checkout will succeed like this:

....

AU        want.bat
U        .
At revision 54722

Then right afterwards I get this svnkit E155007 glitch.

ERROR: Failed to parse svn info for http://svn.ramsoft.biz/core/trunk/powerserver
org.tmatesoft.svn.core.SVNException: svn: E155007: 'E:\workspace\smoketest-delta ' is not a working copy
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:316)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:295)
at org.tmatesoft.svn.core.internal.wc16.SVNWCClient16.crawlEntries(SVNWCClient16.java:3432)
at org.tmatesoft.svn.core.internal.wc16.SVNWCClient16.doInfo(SVNWCClient16.java:2645)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldGetInfo.run(SvnOldGetInfo.java:18)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldGetInfo.run(SvnOldGetInfo.java:12)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2485)
at hudson.scm.SubversionSCM$BuildRevisionMapTask.invoke(SubversionSCM.java:1265)
at hudson.scm.SubversionSCM$BuildRevisionMapTask.invoke(SubversionSCM.java:1233)
at hudson.FilePath.act(FilePath.java:990)
at hudson.FilePath.act(FilePath.java:968)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:835)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
FATAL: null
java.lang.NullPointerException at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:122)
at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:722)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:857)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE

Previous workarounds include modifying Jenkins.xml settings to start the JVM with different command line flags, my Jenkins.xml has this, which as a workaround has worked in the past, neither this nor the alternatives are solving my problem now in Jenkins 2.x, svn plugin 2.5.7

Has anyone seen this?

Warren

[Warren Postma]

Ok I figured it out.  The default working copy format, on the svn plugin is Still 1.4, unless configured otherwise.   Set it to working copy 1.7.  SVNKIT still lacks svn 1.8 and 1.9 working copy option?

Shouldn't the default working copy format be 1.7?  Should I log a bug here, this default behaviour is extremely dated and dangerous. (90% or more of production SVN servers are expecting clients to be using svn 1.7, 1.8 and 1.9).

W