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