Verified with Jenkins 1.472 and Jenkins Subversion Plug-in 1.42, this issue is still present.

Is there any chance that this might be supported?

19:21:45 Checking out a fresh workspace because /var/lib/jenkins/workspace/selenium-server-svn-source/source doesn't exist
19:21:45 Cleaning local Directory ./source
19:21:45 Checking out https://github.com/[...]/selenium-deb-pkg
19:21:48 ERROR: Failed to check out https://github.com/[...]/selenium-deb-pkg
19:21:48 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /[...]/selenium-deb-pkg/!svn/vcc/default failed
19:21:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
19:21:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
19:21:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696)
19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:328)
19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:318)
19:21:48 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:200)
19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:475)
19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getLocations(SVNBasicDelegate.java:838)
19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:527)
19:21:48 at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:925)
19:21:48 at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19)
19:21:48 at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8)
19:21:48 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to