[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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