The SVN format can be specified through the web interface at Manage Jenkins --
Configure System -- Subversion Workspace Version.
Although I think that commit files that I modify in the Jenkins checkout is a
non-standard workflow that you might want to rethink. Can you explain why
you're doing
It is somewhat tricky to integrate out-of-date Jenkins with svn and TortoiseSVN
e.g:
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '/cygdrive/c/jenkins/sdk_build'
is too old (format 29) to work with client version '1.8.9 (r1591380)'
(expects format 31). You
Downgrade TortoiseSVN, or install another SVN (1.7) client to modify the
working copies used in Jenkins.
Jenkins Subversion Plugin does not support SVN 1.8.
On 27.06.2014, at 19:49, Notes Jonny jong...@gmail.com wrote:
It is somewhat tricky to integrate out-of-date Jenkins with svn and
