-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
All
Subversion 1.8 is available but the SVN plugin doesn't support it. For example, Configure|Subversion Workspace Version only offers 1.4 thru 1.7.
https://issues.jenkins-ci.org/browse/JENKINS-18844 is related.
To summarize this instead of having to browse through all the comments:
- Talking to a Subversion 1.8 Server should work fine, however the local working copy will still be SVN <=1.7
- Checking out in Subversion 1.8 Working Copy format does not work, because the version of svnkit that is used in the Subversion plugin (1.7.10) does not support Subversion 1.8 Working Copy
Things that need to be done to make this work:
- svnkit 1.8.0 is available and provides support for Subversion 1.8, see http://svnkit.com/download.php
- Updating to this version and adding "1.8" to the checkbox in the Jenkins Server configuration should be most of what is needed to make it work
- Unfortunately the Subversion plugin uses a patched version of svnkit, see https://github.com/jenkinsci/svnkit, merging the patches and the newer svnkit requires probably some work, depending on the amount of changes in svnkit upstream
- As soon as org.jenkins-ci.svnkit is updated to 1.8.x, the Subversion plugin can upgrade to this and use Subversion 1.8 Working Copy format
- is duplicated by
-
JENKINS-23621 Jenkins using out of date SVN library format 29
-
- Resolved
-
- is related to
-
-
- Resolved
-
[JENKINS-18935] Make Subversion plugin support Subversion 1.8
Preston Gilchrist
added a comment - +1 for this request 
John Salvo
added a comment - Just an FYI ... I had this same issue.
The 1.51 subversion jenkins plugin now uses svnkit 1.7.10, which now allows me to talk to an SVN server running 1.8, which I was not able to do before.
John Salvo
added a comment - Just an FYI ... I had this same issue.
The 1.51 subversion jenkins plugin now uses svnkit 1.7.10, which now allows me to talk to an SVN server running 1.8, which I was not able to do before. 
mark 3000
added a comment - A quick test after upgrading to 1.51 w/ Jenkins 1.518 (Windows) still results in the following error:
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '\Jenkins\workspace\...'
is too old (format 29) to work with client version '1.8.1 (r1503906)' (expects format 31). You need to upgrade the working copy first.
The machine was rebooted and workspace deleted before test results. Implementing the 'svn upgrade' command with a Windows batch script in the job resolves the issue.
mark 3000
added a comment - A quick test after upgrading to 1.51 w/ Jenkins 1.518 (Windows) still results in the following error:
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '\Jenkins\workspace\...'
is too old (format 29) to work with client version '1.8.1 (r1503906)' (expects format 31). You need to upgrade the working copy first.
The machine was rebooted and workspace deleted before test results. Implementing the 'svn upgrade' command with a Windows batch script in the job resolves the issue. 
Yishay Lehman
added a comment - I have SVNVisualServer 2.6 with SVN 1.8, and while able to poll SCM, Jenkins is not able to show the changes or the requests. The console keeps saying that it says: "Checking out a fresh workspace because the workspace is not https://
{XXX}.com/
{Directory}/
{Project}Cleaning local Directory ." and then "no revision recorded". Is this related to the issue?
Yishay Lehman
added a comment - I have SVNVisualServer 2.6 with SVN 1.8, and while able to poll SCM, Jenkins is not able to show the changes or the requests. The console keeps saying that it says: "Checking out a fresh workspace because the workspace is not https://
{XXX}
.com/
{Directory}
/
{Project}
Cleaning local Directory ." and then "no revision recorded". Is this related to the issue?
Peter Thorson
added a comment - Still an issue.
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at 'C:\Apps\Jenkins\jobs\xxxx\workspace'
is too old (format 29) to work with client version '1.8.3 (r1516576)' (expects format 31). You need to upgrade the working copy first.
Not sure if the Sponsor This link is being used by anyone else, but I figured I'd give it a try. I'm willing to throw a couple of bucks after the issue anyway: http://www.freedomsponsors.org/core/issue/362/make-subversion-plugin-support-subversion-18
Peter Thorson
added a comment - Still an issue.
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at 'C:\Apps\Jenkins\jobs\xxxx\workspace'
is too old (format 29) to work with client version '1.8.3 (r1516576)' (expects format 31). You need to upgrade the working copy first.
Not sure if the Sponsor This link is being used by anyone else, but I figured I'd give it a try. I'm willing to throw a couple of bucks after the issue anyway: http://www.freedomsponsors.org/core/issue/362/make-subversion-plugin-support-subversion-18 
Igor Koyfman
added a comment - +1 for this request. 
Brian Spratke
added a comment - +1 for this request 
Tim Bradt
added a comment - BTW...Updating to >= 1.51 of the plugin does allow one to sync a 1.8 repository, but this doesn't help if a) you want to use a newer 1.8 svn client on the target build server and b) you've already upgraded your client and the working copy. The latter results in...
ERROR: svn: E155021: This client is too old to work with the working copy at 'C:\Jenkins' (format '31'). org.tmatesoft.svn.core.SVNException:
Tim Bradt
added a comment - BTW...Updating to >= 1.51 of the plugin does allow one to sync a 1.8 repository, but this doesn't help if a) you want to use a newer 1.8 svn client on the target build server and b) you've already upgraded your client and the working copy. The latter results in...
ERROR: svn: E155021: This client is too old to work with the working copy at 'C:\Jenkins' (format '31'). org.tmatesoft.svn.core.SVNException: Can't believe this issue is not even assigned to anyone?? Since July!
François Dumont
added a comment - - edited Can't believe this issue is not even assigned to anyone?? Since July! 
Christoph Moser
added a comment - +1 for this request 
Damien Finck
added a comment - +1 for this request 
Jason Spotswood
added a comment - I tried using a 1.8.x SVN client with Jenkins. Everything seemed to work fine until I attempted a Maven release which resulted in a failure. Reverting the SVN client to 1.7 resulted in everything working again.
It would be great to get support for 1.8 in place as it has been out for many months now.
Jason Spotswood
added a comment - I tried using a 1.8.x SVN client with Jenkins. Everything seemed to work fine until I attempted a Maven release which resulted in a failure. Reverting the SVN client to 1.7 resulted in everything working again.
It would be great to get support for 1.8 in place as it has been out for many months now. John Salvo
added a comment - Our use case at work is that Jenkins does all the checkout and tagging from and to SVN.
The workspace created by Jenkins Subversion plugin >= 1.51, when checking out of SVN server that is 1.8, is of course in 1.7 working copy format, not 1.8 working copy format. Outside of Jenkins, we don't use any other svn client to access this workspace that is created / checked-out by Jenkins.
Thus, upgrading to Jenkins subversion plug-in 1.51 worked for us.
From the comments here, I see that others are using a different svn client that is a subversion 1.8 client ( which expects a 1.8 working copy format ) on a workspace checked-out by Jenkins subversion plugin >= 1.51 ( which is in 1.7 working copy format ).
What use cases are these ? In these use cases, why can't you use Jenkins subversion plug-in to do all the work related to SVN, including tagging, etc ?
NOTE: I am not a developer for Jenkins or any of the plug-ins. Just asking out of curiosity.
John Salvo
added a comment - Our use case at work is that Jenkins does all the checkout and tagging from and to SVN.
The workspace created by Jenkins Subversion plugin >= 1.51, when checking out of SVN server that is 1.8, is of course in 1.7 working copy format, not 1.8 working copy format. Outside of Jenkins, we don't use any other svn client to access this workspace that is created / checked-out by Jenkins.
Thus, upgrading to Jenkins subversion plug-in 1.51 worked for us.
From the comments here, I see that others are using a different svn client that is a subversion 1.8 client ( which expects a 1.8 working copy format ) on a workspace checked-out by Jenkins subversion plugin >= 1.51 ( which is in 1.7 working copy format ).
What use cases are these ? In these use cases, why can't you use Jenkins subversion plug-in to do all the work related to SVN, including tagging, etc ?
NOTE: I am not a developer for Jenkins or any of the plug-ins. Just asking out of curiosity.
Jason Spotswood
added a comment - In my case, we are using an SVN server at version 1.6. Upgrading to the newer SVN clients has some associated performance benefits, even when the SVN server is at an older release. Thus the reason I am interested in the newer SVN 1.8 client.
As some my Jenkins jobs perform SVN operations within the build shell step, the Jenkins SVN plugin is obviously not used (i.e. I am using the SVN client installed on the assocaited server). But I managed to get all of that to work using a 1.8 SVN client.
What did not work was performing a Maven release. So it seems that Jenkins must use the SVN client installed on the server directly as opposed to entirely relying on the SVN plugin.
Jason Spotswood
added a comment - In my case, we are using an SVN server at version 1.6. Upgrading to the newer SVN clients has some associated performance benefits, even when the SVN server is at an older release. Thus the reason I am interested in the newer SVN 1.8 client.
As some my Jenkins jobs perform SVN operations within the build shell step, the Jenkins SVN plugin is obviously not used (i.e. I am using the SVN client installed on the assocaited server). But I managed to get all of that to work using a 1.8 SVN client.
What did not work was performing a Maven release. So it seems that Jenkins must use the SVN client installed on the server directly as opposed to entirely relying on the SVN plugin. Tim Bradt
added a comment - @JohnSalvo...I don't think you can do commits in your scenario. Most of our development is done on developer PCs, but there are circumstances where it is advantageous to get on the build server (where everything is already built) and make changes and commit. (e.g. - NSIS installers... I don't want to build our entire suite of software just to make/test a change to 1 installer). Our commit message must be of a certain format that includes our JIRA number and description at minimum. You can't really automate commits like that, and the SVN administrator required an upgrade to 1.8.3. This breaks the Jenkins plug-in, so I was forced to create my own script to clean the working copy and update. But I've lost my ability to poll SCM and trigger a build.
Whatever the use case, it's just not a good idea to hold such an intregal part of a CI system back. It needs to be kept up to date.
Tim Bradt
added a comment - @JohnSalvo...I don't think you can do commits in your scenario. Most of our development is done on developer PCs, but there are circumstances where it is advantageous to get on the build server (where everything is already built) and make changes and commit. (e.g. - NSIS installers... I don't want to build our entire suite of software just to make/test a change to 1 installer). Our commit message must be of a certain format that includes our JIRA number and description at minimum. You can't really automate commits like that, and the SVN administrator required an upgrade to 1.8.3. This breaks the Jenkins plug-in, so I was forced to create my own script to clean the working copy and update. But I've lost my ability to poll SCM and trigger a build.
Whatever the use case, it's just not a good idea to hold such an intregal part of a CI system back. It needs to be kept up to date. François Dumont
added a comment - I can add that when using Sonar and the SCM activity plugin, the Sonar analysis fails because the version between SVN server and Jenkins working copy are not compatible.
Jenkins should be up-to-date.
François Dumont
added a comment - I can add that when using Sonar and the SCM activity plugin, the Sonar analysis fails because the version between SVN server and Jenkins working copy are not compatible.
Jenkins should be up-to-date. John Salvo
added a comment - @Tim Bradt, @François Dumont
I am not arguing that Jenkins should not be up-to-date. I completely agree that it should have full support for 1.8. I am not a developer though for Jenkins nor any of its plug-ins .... so I cannot even help at all.
Our use case is that all commits are done from workstations, where everyone is already using Eclipse/Subclipse/svnkit 1.8 or Tortoise SVN 1.8 ..... SVN server at 1.8 ... but Jenkins subversion plug-in is at 1.51 which uses svnkit 1.7.10. Some of our Jenkins jobs also does tagging, etc.
Anything below Jenkins subversion plug-in 1.51 will not allow you to "talk" / poll SVN server 1.8. Hence, I had to wait for subversion plug-in 1.51 ( which uses svnkit 1.7.10 ) before switching the SVN server to 1.8.
Having said that, the Jenkins subversion plugin depends on SVNKIT, and I see that SVNKIT had just came out with 1.8.0-RC1 only 3 days ago, so hopefully, the maintainer of the subversion plug-in will start using svnkit 1.8.0-RC1. Maybe it's just a matter of updating the Subversion plug-in to pull svnkit 1.8.0-RC1 ?
John Salvo
added a comment - @Tim Bradt, @François Dumont
I am not arguing that Jenkins should not be up-to-date. I completely agree that it should have full support for 1.8. I am not a developer though for Jenkins nor any of its plug-ins .... so I cannot even help at all.
Our use case is that all commits are done from workstations, where everyone is already using Eclipse/Subclipse/svnkit 1.8 or Tortoise SVN 1.8 ..... SVN server at 1.8 ... but Jenkins subversion plug-in is at 1.51 which uses svnkit 1.7.10. Some of our Jenkins jobs also does tagging, etc.
Anything below Jenkins subversion plug-in 1.51 will not allow you to "talk" / poll SVN server 1.8. Hence, I had to wait for subversion plug-in 1.51 ( which uses svnkit 1.7.10 ) before switching the SVN server to 1.8.
Having said that, the Jenkins subversion plugin depends on SVNKIT, and I see that SVNKIT had just came out with 1.8.0-RC1 only 3 days ago, so hopefully, the maintainer of the subversion plug-in will start using svnkit 1.8.0-RC1. Maybe it's just a matter of updating the Subversion plug-in to pull svnkit 1.8.0-RC1 ? Tim Bradt
added a comment - @John
Your use case is certainly more convenient.
I hadn't even looked up the actual SVNKIT, but I see what you mean now about how new it is. Hopefully it won't be long before we see the Jenkins plugin updated.
Tim Bradt
added a comment - @John
Your use case is certainly more convenient.
I hadn't even looked up the actual SVNKIT, but I see what you mean now about how new it is. Hopefully it won't be long before we see the Jenkins plugin updated. 
centic
added a comment - Added some status to the description... 
aristedes
added a comment - Please note that svnkit 1.8 final has now been released. François Dumont
added a comment - Still unassigned.. fixed in 6 months? aristedes
added a comment - I think it is pointless being narky about it. I'd love for this to be done, but it appears that Jenkins is using a modified svnkit build which might need to be reviewed and merged. I looked through github to see if I could help, but it was not immediately obvious why or how svnkit was forked.
Hopefully whatever patch was required is no longer needed.
aristedes
added a comment - I think it is pointless being narky about it. I'd love for this to be done, but it appears that Jenkins is using a modified svnkit build which might need to be reviewed and merged. I looked through github to see if I could help, but it was not immediately obvious why or how svnkit was forked.
Hopefully whatever patch was required is no longer needed. 
David Pérez
added a comment - +1 
Lukáš Vasek
added a comment - +1 today I needed to downgrade to 1.7 because of this 
John Knottenbelt
added a comment - +1, really need to 1.8 support. 
Arseniy Arseniy
added a comment - +1, need it "yesterday" 
Dimitar Sakarov
added a comment - +1 
Jens Hirschfeld
added a comment - +1 
Karl Theil
added a comment - +1 
Sergey Saraev
added a comment - +1 
Hendrik Stehr
added a comment - +1 
Peter Schmitz
added a comment - +1 
François Dumont
added a comment - Still not assigned, with so many people who want this 
Egor Sukhanov
added a comment - +1, waiting 
Jeff Behnke
added a comment - +1 
Tim Bradt
added a comment - Latest SVNKIT stable version 1.8.3 as of 1/21/14 fully supports 1.8. Hope we see some activity here soon. +10
Tim Bradt
added a comment - Latest SVNKIT stable version 1.8.3 as of 1/21/14 fully supports 1.8. Hope we see some activity here soon. +10 Sergey Saraev
added a comment - And you can download it from this official repository:
http://maven.tmatesoft.com/content/repositories/releases/
We look forward to.
Sergey Saraev
added a comment - And you can download it from this official repository:
http://maven.tmatesoft.com/content/repositories/releases/
We look forward to. 
Tatiana Chernikova
added a comment - +1 
Alexey Khmelevskikh
added a comment - +1 
Benjamin Urban
added a comment - +1 Peter Thorson
added a comment - There is a merge request now 2 months old to upgrade org.jenkins-ci.svnkit to 1.8.0: https://github.com/jenkinsci/svnkit/pull/2.
But given the Hudson upgrade to 1.8.x just required a change to their pom, I'm hoping we won't need a Jenkins specific SVNKit anymore.
Peter Thorson
added a comment - There is a merge request now 2 months old to upgrade org.jenkins-ci.svnkit to 1.8.0: https://github.com/jenkinsci/svnkit/pull/2 .
But given the Hudson upgrade to 1.8.x just required a change to their pom, I'm hoping we won't need a Jenkins specific SVNKit anymore. 
Doug Rothauser
added a comment - +1 for this request 
Trygve Hardersen
added a comment - +1 (before we have all out projects using Git…) 
Thomas Runge
added a comment - +1 
Jan Wieben
added a comment - +1 If it was at least assigned. We can't start to use Jenkins at at all, until this is implemented.
Jan Wieben
added a comment - +1 If it was at least assigned. We can't start to use Jenkins at at all, until this is implemented. Attached the 2.3-SNAPSHOT build with SVNKit 1.8.4-jenkins-1-SNAPSHOT.
Folks, my apologies for the long wait. I have produced a build of the Subversion plugin that contains 1.8.x versions.
Since this is a major upgrade of SVNKit, I'm hoping to get some feedback from people before we call it a release. Looking forward to hearing back from you.
aristedes
added a comment - Thanks for your tireless work on this project. Out of interest, is svnkit still forked from the official release or have you been able to go back to the main release so that future upgrades will be simpler and less work?
Also, is this plugin set to automatically upgrade the working copy or only when we try to tag or write to the wc?
aristedes
added a comment - Thanks for your tireless work on this project. Out of interest, is svnkit still forked from the official release or have you been able to go back to the main release so that future upgrades will be simpler and less work?
Also, is this plugin set to automatically upgrade the working copy or only when we try to tag or write to the wc? Downloaded and installed subversion Plug-in 2.3-SNAPSHOT (private-03/11/2014 20:58-kohsuke)
Manage Jenkins > Configure System > Subversion > Subversion Workspace Version > Missing option for 1.8
Also, getting a "Cant install ... from pristine store, because no checksum is recorded for this file" checking out a clean workspace. This does not occur when checking out from the same repo using svnkit 1.8.1.10101 with subclipse 1.10.3 in myeclipse.
Mike Konikoff
added a comment - - edited Downloaded and installed subversion Plug-in 2.3-SNAPSHOT (private-03/11/2014 20:58-kohsuke)
Manage Jenkins > Configure System > Subversion > Subversion Workspace Version > Missing option for 1.8
Also, getting a "Cant install ... from pristine store, because no checksum is recorded for this file" checking out a clean workspace. This does not occur when checking out from the same repo using svnkit 1.8.1.10101 with subclipse 1.10.3 in myeclipse.
Hello guys,
Thank you Kohsuke, for you work on jenkins and specifically on this issue.
Unfortunately, this is not working, at least I can't get it to work.
Here is my output checking out a new working folder, don't know if it helps.
Started by user Pedro de Almeida
Building in workspace H:\util
Checking out a fresh workspace because there's no workspace at H:\util
Cleaning local Directory .
Checking out http://eniac/svn/tecinf/trunk/Util at revision '2014-03-13T10:51:33.873 +0000'
A SVNPostCommit
A SVNPostCommit\SVNPostCommit
A SVNPostCommit\SVNPostCommit\SVNPostCommit.csproj
A SVNPostCommit\SVNPostCommit\SvnHelper.cs
A SVNPostCommit\SVNPostCommit\Program.cs
A SVNPostCommit\SVNPostCommit\Properties
A SVNPostCommit\SVNPostCommit\Properties\AssemblyInfo.cs
ERROR: Failed to check out http://eniac/svn/tecinf/trunk/Util
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/tecinf/!svn/vcc/default failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:334)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1305)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:853)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:209)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:72)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:802)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:16)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:10)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1149)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777)
at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:169)
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:133)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1029)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1010)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:986)
at hudson.FilePath.act(FilePath.java:914)
at hudson.FilePath.act(FilePath.java:887)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:935)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:870)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)
at hudson.model.Run.execute(Run.java:1676)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: svn: E175002: REPORT /svn/tecinf/!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)
... 37 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: E155017: REPORT request failed on '/svn/tecinf/!svn/vcc/default'
svn: E155017: Cant install H:\util\SVNPostCommit\SVNPostCommit\SVNPostCommit.csproj from pristine store, because no checksum is recorded for this file
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382)
... 36 more
Caused by: svn: E155017: REPORT request failed on '/svn/tecinf/!svn/vcc/default'
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)
at org.tmatesoft.svn.core.SVNErrorMessage.wrap(SVNErrorMessage.java:407)
... 38 more
Caused by: svn: E155017: Cant install H:\util\SVNPostCommit\SVNPostCommit\SVNPostCommit.csproj from pristine store, because no checksum is recorded for this file
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.wc17.SVNWCContext$RunFileInstall.runOperation(SVNWCContext.java:4008)
at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.dispatchWorkItem(SVNWCContext.java:3941)
at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.wqRun(SVNWCContext.java:3929)
at org.tmatesoft.svn.core.internal.wc17.SVNUpdateEditor17.closeDir(SVNUpdateEditor17.java:1169)
at org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeDir(SVNCancellableEditor.java:102)
at org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(DAVEditorHandler.java:491)
at org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:103)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:917)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:882)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:220)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:480)
... 37 more
java.io.IOException: Failed to check out http://eniac/svn/tecinf/trunk/Util
at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:110)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:169)
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:133)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1029)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1010)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:986)
at hudson.FilePath.act(FilePath.java:914)
at hudson.FilePath.act(FilePath.java:887)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:935)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:870)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)
at hudson.model.Run.execute(Run.java:1676)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/tecinf/!svn/vcc/default failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:334)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1305)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:853)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:209)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:72)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:802)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:16)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:10)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1149)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777)
at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99)
... 19 more
Caused by: svn: E175002: REPORT /svn/tecinf/!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)
... 37 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: E155017: REPORT request failed on '/svn/tecinf/!svn/vcc/default'
svn: E155017: Cant install H:\util\SVNPostCommit\SVNPostCommit\SVNPostCommit.csproj from pristine store, because no checksum is recorded for this file
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382)
... 36 more
Caused by: svn: E155017: REPORT request failed on '/svn/tecinf/!svn/vcc/default'
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)
at org.tmatesoft.svn.core.SVNErrorMessage.wrap(SVNErrorMessage.java:407)
... 38 more
Caused by: svn: E155017: Cant install H:\util\SVNPostCommit\SVNPostCommit\SVNPostCommit.csproj from pristine store, because no checksum is recorded for this file
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.wc17.SVNWCContext$RunFileInstall.runOperation(SVNWCContext.java:4008)
at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.dispatchWorkItem(SVNWCContext.java:3941)
at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.wqRun(SVNWCContext.java:3929)
at org.tmatesoft.svn.core.internal.wc17.SVNUpdateEditor17.closeDir(SVNUpdateEditor17.java:1169)
at org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeDir(SVNCancellableEditor.java:102)
at org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(DAVEditorHandler.java:491)
at org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:103)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:917)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:882)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:220)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:480)
... 37 more
Finished: FAILURE
+1 for this request.