Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:54 PM:
-------------------------------------------------------------
I just tried to check out a fresh copy, which did not succeed.
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder Checking out svn://srv/repopath/trunk/MyFolder ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
Checking out to a 1.6 workspace instead of 1.7 worked with the same configuration.
/e:
Checking out trunk to a 1.7 workspace fails as well, same error.
/e:
Checking out a 1.7 working copy manually - to the target path - before the build starts (so, without jenkins),
jenkins does run an update on the working copy, the checked out path.
Going back to an older revision on the 1.7 working copy Jenkins does indeed update to HEAD.
Just the new checkout to 1.7 workspace seems to fail.
was (Author: jk):
I just tried to check out a fresh copy, which did not succeed.
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder Checking out svn://srv/repopath/trunk/MyFolder ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
Checking out to a 1.6 workspace instead of 1.7 worked with the same configuration.
/e:
Checking out trunk to a 1.7 workspace fails as well, same error.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Kohsuke Kawaguchi commented on JENKINS-11381:
---------------------------------------------
There has been and is a global configuration where you choose the working copy format version. So if the auto-upgrade is possible with SVNKit, I don't see any harm in doing so when this global configuration points to 1.7. The main problem right now for me is that I don't know how to make it happen.
Jan, what is the Subversion server version? You said you saw that error while you were checking out to 1.7 workspace format? Also, please don't truncate the stack trace, because it is invaluable for me to understand where things failed.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Jan Klass commented on JENKINS-11381:
-------------------------------------
On the questions Kohsuke asked:
> When this error happens, do you have C:\Data\Jenkins\workspace\job\src\.svn? I step executed the code and it does create the workspace right before the code gets to here.
No. Neither the .svn folder nor the folder it should be placed in is being created.
Even if I create the target folder myself, no .svn folder is being created.
> The other experiment I'd like you to try is to use the scripting console, run "org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.ourFactories; ", and report back what you see. I wonder if someone else is setting that collection to empty, which would explain this.
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:58 PM:
-------------------------------------------------------------
On the questions Kohsuke asked:
{quote}When this error happens, do you have C:\Data\Jenkins\workspace\job\src\.svn? I step executed the code and it does create the workspace right before the code gets to here.{quote}
No. Neither the .svn folder nor the folder it should be placed in is being created.
Even if I create the target folder myself, no .svn folder is being created.
{quote}The other experiment I'd like you to try is to use the scripting console, run "org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.ourFactories; ", and report back what you see. I wonder if someone else is setting that collection to empty, which would explain this.{quote}
> When this error happens, do you have C:\Data\Jenkins\workspace\job\src\.svn? I step executed the code and it does create the workspace right before the code gets to here.
No. Neither the .svn folder nor the folder it should be placed in is being created.
Even if I create the target folder myself, no .svn folder is being created.
> The other experiment I'd like you to try is to use the scripting console, run "org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.ourFactories; ", and report back what you see. I wonder if someone else is setting that collection to empty, which would explain this.
Jan Klass commented on JENKINS-11381:
-------------------------------------
Here is the full stack trace. Path/Folder-names replaced.
MyFolder1 is a 1.7 working copy I checked out manually before-hand.
MyFolder2 is the Path it is supposed to check out as a 1.7 working copy.
{quote}
Gestartet durch Benutzer anonymous
Baue auf Slave local2 in workspace c:\jenkins\workspace\Proj Name
Updating svn://srv/path/ProjRepo/trunk/MyFolder1
At revision 32522
Checking out a fresh workspace because there's no workspace at C:\jenkins\workspace\Proj Name\MyFolder2
Cleaning local Directory MyFolder2
Checking out svn://srv/path/ProjRepo/trunk/MyFolder2
ERROR: Failed to check out svn://srv/path/ProjRepo/trunk/MyFolder2
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\Proj Name\MyFolder2' is not a working copy
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.ja va:64)
at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminA reaFactory.java:170)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.jav a:379)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java: 283)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java: 276)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess .java:171)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClie nt16.java:514)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdate Client16.java:965)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.j ava:19)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.j ava:8)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunn er.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java :1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:7 81)
at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:86)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdat er.java:144)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdat er.java:152)
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121 )
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdat er.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorServ ice.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
Caused by: svn: E155007: 'C:\jenkins\workspace\Proj Name\MyFolder2' is not a working copy
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126)
at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminA reaFactory.java:165)
... 31 more
FATAL: null
java.lang.NullPointerException
at java.util.ArrayList.addAll(Unknown Source)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
{quote}
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Jan Klass commented on JENKINS-11381:
-------------------------------------
On my RC1 problem: SVN version is 1.7 as well (thought you wanted a more specific version). Just as working copy format in global configuration, which is 1.7 as well.
Will try out the new RC.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Jan Klass edited comment on JENKINS-11381 at 5/9/12 7:07 AM:
-------------------------------------------------------------
On my RC1 problem: SVN version is 1.7 as well (thought you wanted a more specific version). Just as working copy format in global configuration, which is 1.7 as well. Accessed via svn protocol.
Will try out the new RC.
was (Author: jk):
On my RC1 problem: SVN version is 1.7 as well (thought you wanted a more specific version). Just as working copy format in global configuration, which is 1.7 as well.
Will try out the new RC.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Jan Klass commented on JENKINS-11381:
-------------------------------------
RC3 checks out the 1.7 working copy just fine.
The tag-listing seems to work fine as well, they are listed as described. Checking a selected tag out to a 1.7 working copy seems to work fine as well. (I did not try selecting from the repo root but from a tags/branches folder as we have them not in first path level of tags/branches.)
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
ntumba lobo commented on JENKINS-11381:
---------------------------------------
Thank for the work on this issue.
I would benefit from it but I dont understand the release number mentioned by Kohsuke Kawaguchi 1.40.
What does it refer to ? Our current Jenkins version is already 1.447.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
brenuart commented on JENKINS-11381:
------------------------------------
{quote}
I would benefit from it but I dont understand the release number mentioned by Kohsuke Kawaguchi 1.40.
{quote}
1.40 is the version of the *Subversion Plugin*. Go into "Manage Jenkins"->"Manage Plugins": the "Installed" tab lists the plugins installed on your instance and their corresponding versions.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Duncan Perrett commented on JENKINS-11381:
------------------------------------------
I found it a bit confusing as the subversion plugin is one that is bundled with jenkins.
However, the latest jenkins.war bundle includes a much older version of the subversion plugin so you need to manually update it.
(I don't know when/if the bundled version will ever reach 1.40).
I think this is called 'pinning' the plugin.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Diane Wills commented on JENKINS-11381:
---------------------------------------
I'm still not able to update Jenkins to use the Subversion Plugin 1.40. I'm using Jenkins 1.466 on Windows Server 2008. I tried manually updating the Subversion files and writing the empty file Subversion.jpi.pinned to $(JENKINS_HOME)/plugins, but that didn't work; the files got overwritten anyways to the old version.
Since there are no plans to add Subversion 1.40 to Jenkins permanently, can someone help me?
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Denis Eperonnier commented on JENKINS-11381:
--------------------------------------------
I noticed something strange using Subversion Plugin 1.40, together with Jenkins 1.467.
Some time after the upgrade from plugin 1.39, there were some errors when trying to update a slave workspace:
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/xxxxxxxxxx/!svn/vcc/default failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:304)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:289)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:277)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAV Connection.java:696)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection .java:328)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepositor y.java:1289)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.j ava:837)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClie nt16.java:557)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateCl ient16.java:414)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateCl ient16.java:324)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java: 27)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java: 11)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunn er.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java :1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315 )
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295 )
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391 )
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136 )
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdat er.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorServ ice.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
Caused by: svn: E175002: REPORT /svn/xxxxxxxx/!svn/vcc/default failed
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 34 more
no change for http://xxxxxxxxx since the previous build
So I checked svn server log, and I could see that my master node uses the latest SVNKit 1.7.4 ("SVN/1.7.4 SVNKit/1.7.4-jenkins-1 (http://svnkit.com/) t20120507_1224"), but one of my slaves is using an older version ("SVN/1.7.0 SVNKit/1.7.0-dev (http://svnkit.com/) rSNAPSHOT"), can this explain my issue?
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
Denis Eperonnier edited comment on JENKINS-11381 at 6/11/12 9:10 PM:
---------------------------------------------------------------------
I noticed something strange using Subversion Plugin 1.40, together with Jenkins 1.467.
Some time after the upgrade from plugin 1.39, there were some errors when trying to update a slave workspace:
{quote}
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/xxxxxxxxxx/!svn/vcc/default failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:304)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:289)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:277)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAV Connection.java:696)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection .java:328)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepositor y.java:1289)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.j ava:837)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClie nt16.java:557)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateCl ient16.java:414)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateCl ient16.java:324)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java: 27)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java: 11)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunn er.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java :1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315 )
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295 )
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391 )
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136 )
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdat er.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorServ ice.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
Caused by: svn: E175002: REPORT /svn/xxxxxxxx/!svn/vcc/default failed
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 34 more
no change for http://xxxxxxxxx since the previous build
{quote}
So I checked svn server log, and I could see that my master node uses the latest SVNKit 1.7.4 ("SVN/1.7.4 SVNKit/1.7.4-jenkins-1 (http://svnkit.com/) t20120507_1224"), but one of my slaves is using an older version ("SVN/1.7.0 SVNKit/1.7.0-dev (http://svnkit.com/) rSNAPSHOT"), can this explain my issue?
was (Author: depe):
I noticed something strange using Subversion Plugin 1.40, together with Jenkins 1.467.
Some time after the upgrade from plugin 1.39, there were some errors when trying to update a slave workspace:
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/xxxxxxxxxx/!svn/vcc/default failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:304)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:289)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConn ection.java:277)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAV Connection.java:696)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection .java:328)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepositor y.java:1289)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.j ava:837)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClie nt16.java:557)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateCl ient16.java:414)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateCl ient16.java:324)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java: 27)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java: 11)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunn er.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java :1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315 )
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295 )
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391 )
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136 )
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdat er.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorServ ice.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
Caused by: svn: E175002: REPORT /svn/xxxxxxxx/!svn/vcc/default failed
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 34 more
no change for http://xxxxxxxxx since the previous build
So I checked svn server log, and I could see that my master node uses the latest SVNKit 1.7.4 ("SVN/1.7.4 SVNKit/1.7.4-jenkins-1 (http://svnkit.com/) t20120507_1224"), but one of my slaves is using an older version ("SVN/1.7.0 SVNKit/1.7.0-dev (http://svnkit.com/) rSNAPSHOT"), can this explain my issue?
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
