[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
Kohsuke Kawaguchi resolved JENKINS-11381 as Fixed Subversion Plugin does not support Subversion 1.7 Richard, Denis, if you see issues with Subversion plugin, please open a separate ticket instead of reopening this. This ticket was to track the integration of SVNKit 1.7 that brings in Subversion 1.7 compatibility, and that work is completed. In the event that this work introduced issues, please use a separate ticket, so that we can track issues better. Thanks! Change By: Kohsuke Kawaguchi (23/Jun/12 2:27 AM) Status: Reopened Resolved Resolution: Fixed 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
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163826#comment-163826 ] 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/xx/!svn/vcc/default failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.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(DAVRepository.java:1289) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.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(SvnOperationRunner.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(WorkspaceUpdater.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(InterceptingExecutorService.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//!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://x 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 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Assignee: Kohsuke Kawaguchi Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163826#comment-163826
]
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/xx/!svn/vcc/default failed
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.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(DAVRepository.java:1289)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
at
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557)
at
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414)
at
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.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(SvnOperationRunner.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(WorkspaceUpdater.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(InterceptingExecutorService.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//!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://x 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/xx/!svn/vcc/default failed
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
at
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Villanueva reopened JENKINS-11381: -- It is not resolved Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Assignee: Kohsuke Kawaguchi Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163491#comment-163491 ] 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 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Assignee: Kohsuke Kawaguchi Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163000#comment-163000 ] 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 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Assignee: Kohsuke Kawaguchi Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163002#comment-163002
]
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
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Assignee: Kohsuke Kawaguchi
Priority: Blocker
Attachments: subversion.hpi, subversion.hpi, subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi resolved JENKINS-11381. - Assignee: Kohsuke Kawaguchi Resolution: Fixed Released as 1.40. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Assignee: Kohsuke Kawaguchi Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162593#comment-162593 ] 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 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162593#comment-162593 ] 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 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162600#comment-162600 ] Jan Klass commented on JENKINS-11381: - Thank you very much for your work, looking forward to the release! Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162534#comment-162534 ] John Salvo commented on JENKINS-11381: -- Out of curiosity, those experiencing long delays during any SVN operation when they upgraded their SVN plugin to use 1.7/1.8 format .. did you upgrade your working copy from 1.6 to 1.7/1.8 format first ? http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng To quote: Upgrading the Working Copy Subversion 1.7 introduces substantial changes to the working copy format. In previous releases of Subversion, Subversion would automatically update the working copy to the new format when a write operation was performed. Subversion 1.7, however, will make this a manual step. Before using Subversion 1.7 with their working copies, users will be required to run a new command, svn upgrade to update the metadata to the new format. This command may take a while, and for some users, it may be more practical to simply checkout a new working copy. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162534#comment-162534 ] John Salvo edited comment on JENKINS-11381 at 5/8/12 11:21 AM: --- Out of curiosity, those experiencing long delays during any SVN operation when they upgraded their SVN plugin to use 1.7 format .. did you upgrade your working copy from 1.6 to 1.7 format first ? http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng To quote: Upgrading the Working Copy Subversion 1.7 introduces substantial changes to the working copy format. In previous releases of Subversion, Subversion would automatically update the working copy to the new format when a write operation was performed. Subversion 1.7, however, will make this a manual step. Before using Subversion 1.7 with their working copies, users will be required to run a new command, svn upgrade to update the metadata to the new format. This command may take a while, and for some users, it may be more practical to simply checkout a new working copy. was (Author: salvojo): Out of curiosity, those experiencing long delays during any SVN operation when they upgraded their SVN plugin to use 1.7/1.8 format .. did you upgrade your working copy from 1.6 to 1.7/1.8 format first ? http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng To quote: Upgrading the Working Copy Subversion 1.7 introduces substantial changes to the working copy format. In previous releases of Subversion, Subversion would automatically update the working copy to the new format when a write operation was performed. Subversion 1.7, however, will make this a manual step. Before using Subversion 1.7 with their working copies, users will be required to run a new command, svn upgrade to update the metadata to the new format. This command may take a while, and for some users, it may be more practical to simply checkout a new working copy. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162535#comment-162535 ] Peter Lillevold commented on JENKINS-11381: --- The question is: will the new SVNKit do an automatic working copy upgrade? Or are we better of scrapping all our existing working copies? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162536#comment-162536 ] Jan Klass commented on JENKINS-11381: - An automatic upgrade should definitely not be the way to go, as workspaces, tool- and build-chains may depend on the old working copy structure. Maybe a flag setting for enabling an automatic upgrade when the old format is identified would be an option. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162538#comment-162538 ] brenuart commented on JENKINS-11381: Don't see any benefit of having such an auto upgrade feature... What's the problem in just dropping the workspaces and let Jenkins checkout the projects again ? It's just a one-time operation... Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162542#comment-162542 ] Dan Lewis commented on JENKINS-11381: - agree. bonus points if we can fail fast with an appropriate error message explaining corrective procedure, e.g. jenkins does not support auto-update of pre-SVN 1.7 workspaces to 1.7; please remove workspaces and restart build or some such Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162543#comment-162543 ] Jan Klass commented on JENKINS-11381: - I installed version 140RC locally. The parametrized build (List subversion tags and more) only lists trunk. See also the other ticket https://issues.jenkins-ci.org/browse/JENKINS-11933?focusedCommentId=162399#comment-162399 On Configuration: The repository is being accepted as valid, root path as well as subpaths. Did not check out on it yet. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162544#comment-162544
]
Jan Klass commented on JENKINS-11381:
-
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}
Subversion Plugin does not support Subversion 1.7
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
Attachments: subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162544#comment-162544
]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:12 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 settings.
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}
Subversion Plugin does not support Subversion 1.7
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
Attachments: subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162544#comment-162544
]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:12 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.
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 settings.
Subversion Plugin does not support Subversion 1.7
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
Attachments: subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162544#comment-162544
]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:14 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.
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.
Subversion Plugin does not support Subversion 1.7
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
Attachments: subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162546#comment-162546 ] 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 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162547#comment-162547
]
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.
{quote}
Result:
[org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory@1b4d6c0,
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea15Factory@17f0649,
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14Factory@75c229,
org.tmatesoft.svn.core.internal.wc.admin.SVNXMLAdminAreaFactory@11e4232]
{quote}
Subversion Plugin does not support Subversion 1.7
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
Attachments: subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162547#comment-162547
]
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}
{quote}
Result:
[org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory@1b4d6c0,
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea15Factory@17f0649,
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14Factory@75c229,
org.tmatesoft.svn.core.internal.wc.admin.SVNXMLAdminAreaFactory@11e4232]
{quote}
was (Author: jk):
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.
{quote}
Result:
[org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory@1b4d6c0,
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea15Factory@17f0649,
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14Factory@75c229,
org.tmatesoft.svn.core.internal.wc.admin.SVNXMLAdminAreaFactory@11e4232]
{quote}
Subversion Plugin does not support Subversion 1.7
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
Attachments: subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162544#comment-162544
]
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
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
Attachments: subversion.hpi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162550#comment-162550
]
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.java:64)
at
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:170)
at
org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java: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(SVNUpdateClient16.java:514)
at
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:965)
at
org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19)
at
org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8)
at
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.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:781)
at
hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:86)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:152)
at
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.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(InterceptingExecutorService.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(SVNAdminAreaFactory.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
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162552#comment-162552 ] Kohsuke Kawaguchi commented on JENKINS-11381: - I was ablt to reproduce [Alexsei's problem|https://issues.jenkins-ci.org/browse/JENKINS-11381?focusedCommentId=162505page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-162505] by checking out from 1.7 subversion server to 1.7 working copy format via svn:// protocol. Looking into it. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162553#comment-162553 ] Kohsuke Kawaguchi commented on JENKINS-11381: - For those who are reporting issues with 1.40 RC, please also report: * version of the Subversion server (=1.7 or 1.7?) * working copy format you set in the global configuration * Subversion access protocol Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi updated JENKINS-11381: Attachment: subversion.hpi Attached 1.40 RC2 built from rev.40558 in the repository. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi updated JENKINS-11381: Attachment: subversion.hpi And this is 1.40 RC3 that fixes the list tags/branches parameter problem. From the repository revision 40560. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162557#comment-162557 ] Kohsuke Kawaguchi edited comment on JENKINS-11381 at 5/8/12 5:33 PM: - And [this is 1.40 RC3|https://issues.jenkins-ci.org/secure/attachment/21803/subversion.hpi] that fixes the list tags/branches parameter problem. From the repository revision 40560. was (Author: kohsuke): And this is 1.40 RC3 that fixes the list tags/branches parameter problem. From the repository revision 40560. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi, subversion.hpi, subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi updated JENKINS-11381: Attachment: subversion.hpi Uploaded 1.40 RC that supports Subversion 1.7 Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162502#comment-162502 ] Kohsuke Kawaguchi edited comment on JENKINS-11381 at 5/7/12 8:38 PM: - [Uploaded 1.40 RC|https://issues.jenkins-ci.org/secure/attachment/21796/subversion.hpi] that supports Subversion 1.7. I'm running this on http://ci.jenkins-ci.org/ now, but any additional beta testing appreciated. It does pass all the tests we have, but there are major changes in SVNKit, so I'm being bit cautious. was (Author: kohsuke): Uploaded 1.40 RC that supports Subversion 1.7 Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162505#comment-162505 ] Alexei Turchanikov commented on JENKINS-11381: -- I just tried the 1.40 RC, it throws an exception when attempting to check out to a directory that isn't a working copy (such as when Always check out a fresh copy is selected or if this is the first build): ERROR: Failed to check out https://domain/svn/repo org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\Data\Jenkins\workspace\job\src' 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.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:170) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java: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(SVNUpdateClient16.java:514) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:965) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.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:781) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:86) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.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.act(FilePath.java:832) at hudson.FilePath.act(FilePath.java:814) 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:581) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470) 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) Caused by: svn: E155007: 'C:\Data\Jenkins\workspace\job\src' 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(SVNAdminAreaFactory.java:165) ... 28 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:581) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470) 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) Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162522#comment-162522 ] Kohsuke Kawaguchi commented on JENKINS-11381: - Alexei, I couldn't reproduce the problem. 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. 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. I continue to look for other people trying out this version. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker Attachments: subversion.hpi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162439#comment-162439 ] Richard Villanueva commented on JENKINS-11381: -- Hi, We also are waiting for this update for 2 months, it should be great because of the SVN migration is postponed until the compatibility between our Jenkins platform and our new SVN plaform is made; Good luke for the final lap of merging your work in the next release of Jenkins Regards Richard Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162079#comment-162079 ] Dmitry Teterevyatnikov commented on JENKINS-11381: -- Great job Centric! Thank you. I haven't tried your patches (because fo have no idea how to use them), but does anyone knows how this fix can be forced to be processed into the product? This Jira is the most voted blocker in this project, why it is not assigned to anyone who have rights to include fixes in the product? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162083#comment-162083 ] Robert Lachner commented on JENKINS-11381: -- @Dimitry ok, just tried 60MB checkout on a Virtual Machine with Jenkins 1.461, SVN Plugin 1.34 and VisualSVN 2.5.4(the Version with SVN 1.7.4), it takes about 30seconds. Nothing unusual so far... Maybe the older 1.34 Version does not have this long checkout behaviour ? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162083#comment-162083 ] Robert Lachner edited comment on JENKINS-11381 at 4/26/12 10:53 AM: @Dimitry ok, just tried 60MB checkout on a Virtual Machine with Jenkins 1.461, SVN Plugin 1.34 and VisualSVN 2.5.4(the Version with SVN 1.7.4), it takes about 30seconds. Nothing unusual so far... Maybe the older 1.34 Version does not have this long checkout behaviour ? ...just tried with updated Plugin to 1.39, same result was (Author: heinzepreller0815): @Dimitry ok, just tried 60MB checkout on a Virtual Machine with Jenkins 1.461, SVN Plugin 1.34 and VisualSVN 2.5.4(the Version with SVN 1.7.4), it takes about 30seconds. Nothing unusual so far... Maybe the older 1.34 Version does not have this long checkout behaviour ? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162086#comment-162086 ] jbuchberger commented on JENKINS-11381: --- FWIW, svnkit 1.7.4 hit maven central and should be generally available Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162022#comment-162022 ] centic commented on JENKINS-11381: -- Please hold on for just a bit longer, I managed to merge the necessary pieces and started local testing yesterday, so far it looks promising. I'll try to post an updated hack-build of the plugin and put all the necessary changes (svnkit/trilead-ssh2/subversion-plugin) on github so they can be reviewed and applied to the official sources easily. (I am not associated with any of these projects currently, so I cannot do offical builds here) Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162045#comment-162045 ] centic commented on JENKINS-11381: -- Please give the plugin available at JENKINS-11933 a try now, I did a minimal bit of local verification, so far it works for me. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161914#comment-161914 ] Dmitry Teterevyatnikov commented on JENKINS-11381: -- @centric: Thanks for the patch. But it looks like even with your patch we still have a problem with full SVN 1.7 support by Jenkins. I.e. currently on our build environments, Jenkins works fine with SVN 1.7 with old 1.6 SVN format. Everithing works correct, but.. performance of all SVN related operations is horrible. I.e. checkout of SVN 1.7 trunk by Jenkins with size about 100 MB takes about 30-40 minutes. Due to SVN 1.6 working format is used by current version of Jenkins SVN plugin, newest command-line SVN clients works with old SVN 1.6 format really slow. At the result our releases takes more then hour, where 40 minutes - it is a SVN-related tasks. I am totally sure that update of Subversion plugin on Jenkins to latest SVNKit will fix all SVN performance re;lated problems. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161969#comment-161969 ] centic commented on JENKINS-11381: -- Sorry, I already gave it a try and started the merge of 1.7.4 and the jenkins-specific changes, but there are a lot of conflicts and I lack some knowledge about the changes in the jenkins-version to tell me how to solve them... Maybe I try again and see if a hacky-wacky merge leads at least to a workable solution... Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161888#comment-161888 ] Dmitry Teterevyatnikov commented on JENKINS-11381: -- Looks like Jenkins Jira is dead... really strange for a so popular service/product. Does anyone knows how to force this issue to be resolved (together with voiting)? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161893#comment-161893 ] Mark Dreyer commented on JENKINS-11381: --- The hudson team did some work on this that included removing the customization to svn kit. If the same can be done with jenkins, you could just use the new svnkit library. See http://issues.hudson-ci.org/browse/HUDSON-9111 for more info. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161894#comment-161894 ] Jamie Press commented on JENKINS-11381: --- In JENKINS-11933, the 'duplicate' issue for this, someone added a patch file that theoretically upgrades the svnkit version from the defective 1.3.6.1 to the partially working 1.3.7 (this version can apparently speak to the 1.7.x server, though not 1.7.x working copy). As I would guess that most of us are only using Jenkins to check out the latest version, this may serve as a workaround for many. However, applying a patch file is a little beyond my expertise. Is anyone able to see if that patch works, and if so, post the patched svnkit? It apparently makes a version called 1.3.7-jenkins-0. All that being said, Dreyguy is right in saying the Hudson team made the right move. Decoupling the svnkit from the plugin would be desirable. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161902#comment-161902 ] centic commented on JENKINS-11381: -- I have now attached the .hpi file that I use locally for getting at least 1.7-server supported in Jenkins to JENKINS-11933. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161910#comment-161910 ] hyunsoo lee commented on JENKINS-11381: --- Thanks a lot!!! centic!! It's working Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161800#comment-161800 ] Jamie Press commented on JENKINS-11381: --- SVNKit 1.7.4 is now out, which does allow functionality with both 1.7 server and working copies... /hopeful glance? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161716#comment-161716 ] Qin Ding commented on JENKINS-11381: There is my workaround : 1. Install the latest CollabNet Subversion Client to the server, which provides svn command-line tool. 2. Put all maven commands into a shell, i.e. bat for Windows. 3. Use maven-antrun-plugin to execute that shell. 4. In Jenkins configuration page, just use 'antrun:run' as the 'Goals and options'. It works because the shell will use the system variable where PATH includes the latest CollabNet path rather than the old svn path used by Jenkins. My website : http://softhinker.com Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161730#comment-161730 ] Jeremy Truelove commented on JENKINS-11381: --- Not everyone uses ant/maven Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161733#comment-161733 ] Dmitry Teterevyatnikov commented on JENKINS-11381: -- I am agree with Jeremy, i.e. everyone wants to use the Jenkins with all its features from the box with the best performance. Does anyone knows how to speedUp this issue to be resolved? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161735#comment-161735 ] Matthias Ulrich commented on JENKINS-11381: --- I also want to point out, that the workaround is not applicable to all use cases of Jenkins and that this is a show stopper in some situation. So as svnkit for svn1.7 is availble, this issue should be assigned as it is a showstopper/Blocker. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161735#comment-161735 ] Matthias Ulrich edited comment on JENKINS-11381 at 4/18/12 3:03 PM: I also want to point out, that the workaround is not applicable to all use cases of Jenkins and that this is a show stopper in some situations. So as svnkit for svn 1.7 is availble now, this issue should be assigned as it is a Blocker. was (Author: mulrich): I also want to point out, that the workaround is not applicable to all use cases of Jenkins and that this is a show stopper in some situation. So as svnkit for svn1.7 is availble, this issue should be assigned as it is a showstopper/Blocker. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161737#comment-161737 ] Jan Klass commented on JENKINS-11381: - @Dmitry: The only thing you can do to speed up the process is * vote on this issue (left of top right) * fix / implement it yourself and commit / provide patch/diff Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161739#comment-161739 ] Jay Beeckman commented on JENKINS-11381: Jan, I have considered trying to get the fix in myself. If I wasn't so busy right now I would. This is holding up a big integration we have done with our delivery process, so it's killing me, but not something I could do right away. I do like your suggestion of voting, more voices the better :-) Jay Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161690#comment-161690 ] J T commented on JENKINS-11381: --- Any updates on this? It appears there is a stable release of SVNKit which supports 1.7 Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161545#comment-161545
]
Gustavo Chaves commented on JENKINS-11381:
--
SVNKit 1.7.4 has just been released. The [download
page|http://svnkit.com/download.php] says this:
{quote}
Lastest stable version of SVNKit (*1.7.4*) is *compatible* with Subversion 1.7
working copy format and with Subversion 1.7 servers.
{quote}
Subversion Plugin does not support Subversion 1.7
-
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
Priority: Blocker
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161388#comment-161388 ] Jay Beeckman commented on JENKINS-11381: This is according to SVNKit's web page (http://svnkit.com/download.php): Lastest stable version of SVNKit (1.3.7) is not compatible with Subversion 1.7 working copy format. However, SVNKit 1.7 is under development now and we plan to release it in 12th of April 2012. We plan to publish first Release Candidate build till the end of February 2012. This is in three days, when could we reasonably expect this to be rolled into the plugin if they do indeed release on the 12th? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161188#comment-161188 ] Jay Beeckman commented on JENKINS-11381: Any update on this? It appears that SVNKIT has updated their stuff? An ETA would be great. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161189#comment-161189 ] Milutin Jovanovic commented on JENKINS-11381: - I am not the maintainer, but interested in this... SVNKit is still in release candidate stage, so I don't think svn plugin will be updated until SVNKit is fully released. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160639#comment-160639 ] Chris Platts commented on JENKINS-11381: Hi, I've got a few projects which perform a svn commit as part of their build process (a script updates version numbers to match the build/revision before committing those changes back to the repository). As a workaround, I've added an 'svn upgrade .' command before the 'svn commit .' statement. This means that the old-format working dir created by Jenkins is able to be committed at the end of the build. This works, but almost doubles the time that each build takes. I'm really looking forward to an update to this plugin to support v1.7 working copies. Of course, as mentioned, I'd also have no problem with an option to use the native svn client. Thanks, Chris Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159216#comment-159216 ] Milutin Jovanovic commented on JENKINS-11381: - Is there some sort of ETA for this fix? Jenkins SVN depends on SVNKIT. They have been promising a new version for a while, but always ran into trouble. Currently their web site says release Feb 2012, but since they are about to release beta, I am guessing March. It's a guess. I am sure Jenkins SVN people will update the plugin as soon as the underlying library is updated. In that case you're dependent on having the user installed the 'right' version of the native svn client. I'm not sure if that is the better alternative. It worked fine for Netbeans for months... Jumping through some hoops is prefereable to it not working at all. I fourth this. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159102#comment-159102 ] Roland Zwaga commented on JENKINS-11381: Is there some sort of ETA for this fix? I have quite a few projects that can no longer be built by Jenkins. I understand OS work is mostly done in people's spare time, but a rough estimate of when this can be fixed would be really appreciated. Thanks a lot in advance. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159124#comment-159124 ] kutzi commented on JENKINS-11381: - Why not allow usage of the command line client, instead of just SVNKit? At least this way, you're not always dependent on a particular downstream product? In that case you're dependent on having the user installed the 'right' version of the native svn client. I'm not sure if that is the better alternative. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
