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