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 need to upgrade the working copy first. $ svn --version svn, version 1.8.9 (r1591380) compiled May 14 2014, 22:20:14 on i686-pc-cygwin TortoiseSVN: TortoiseSVN 1.8.5, Build 25224 - 32 Bit , 2014/02/18 20:05:11 Subversion 1.8.8, -release But Jenkins is using out of date: Subversion Workspace version 1.7 Any ideas? On Fri, Jun 27, 2014 at 10:46 AM, Notes Jonny <jong...@gmail.com> wrote: > Hello > > I installed Jenkins 1.568 on a Windows7 machine that has latest > TortoiseSVN. Unfortunately I see Jenkins is using a much older repo > format. > > Could Jenkins be updated to use latest SVN repo format? It is very > inconvenient that I can't commit files that I modify in the Jenkins > checkout.. > Jon -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.