• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • subversion-plugin
    • None
    • All

      Subversion 1.8 is available but the SVN plugin doesn't support it. For example, Configure|Subversion Workspace Version only offers 1.4 thru 1.7.

      https://issues.jenkins-ci.org/browse/JENKINS-18844 is related.


      To summarize this instead of having to browse through all the comments:

      • Talking to a Subversion 1.8 Server should work fine, however the local working copy will still be SVN <=1.7
      • Checking out in Subversion 1.8 Working Copy format does not work, because the version of svnkit that is used in the Subversion plugin (1.7.10) does not support Subversion 1.8 Working Copy

      Things that need to be done to make this work:

      • svnkit 1.8.0 is available and provides support for Subversion 1.8, see http://svnkit.com/download.php
      • Updating to this version and adding "1.8" to the checkbox in the Jenkins Server configuration should be most of what is needed to make it work
      • Unfortunately the Subversion plugin uses a patched version of svnkit, see https://github.com/jenkinsci/svnkit, merging the patches and the newer svnkit requires probably some work, depending on the amount of changes in svnkit upstream
      • As soon as org.jenkins-ci.svnkit is updated to 1.8.x, the Subversion plugin can upgrade to this and use Subversion 1.8 Working Copy format

          [JENKINS-18935] Make Subversion plugin support Subversion 1.8

          Karl Theil added a comment -

          this is an other issue im confronted with too: https://issues.jenkins-ci.org/browse/JENKINS-26318

          Karl Theil added a comment - this is an other issue im confronted with too: https://issues.jenkins-ci.org/browse/JENKINS-26318

          Smouch Smouch added a comment -

          Does this:

          Version 2.5 (Jan 2, 2015)
          Replace custom svnkit library in exchange for using the default binaries.
          issue #18935 Upgrade to svn 1.8.
          issue #25241 Upgrade trilead-ssh.

          mean that there is a way to use the hosts version of subversion instead of the Jenkins built-in (plug-in whatever) version ?

          I find the whole topic of subversion support within Jenkins quite confusing.
          I don't understand why Jenkins would ever ship with a plug-in installed by default in such a way that's it's not really a plug-in. I also don't understand why there is a separate plug-in that can be a different version from the one shipped by default.

          I also don't understand why Jenkins would have a subversion plug-in at all. Jenkins is a front end to cron, and of course needs to display results. That there are so many - some conflicting - plug-ins may be considered a strength, but it also means there are simply too many options for failure.

          Jenkins should be should be able to communicate with anything, but not require a "plug-in" or built-in functionality to reproduce (usually incorrectly) or mimic that behavior.

          Smouch Smouch added a comment - Does this: Version 2.5 (Jan 2, 2015) Replace custom svnkit library in exchange for using the default binaries. issue #18935 Upgrade to svn 1.8. issue #25241 Upgrade trilead-ssh. mean that there is a way to use the hosts version of subversion instead of the Jenkins built-in (plug-in whatever) version ? I find the whole topic of subversion support within Jenkins quite confusing. I don't understand why Jenkins would ever ship with a plug-in installed by default in such a way that's it's not really a plug-in. I also don't understand why there is a separate plug-in that can be a different version from the one shipped by default. I also don't understand why Jenkins would have a subversion plug-in at all. Jenkins is a front end to cron, and of course needs to display results. That there are so many - some conflicting - plug-ins may be considered a strength, but it also means there are simply too many options for failure. Jenkins should be should be able to communicate with anything, but not require a "plug-in" or built-in functionality to reproduce (usually incorrectly) or mimic that behavior.

          Daniel Beck added a comment -

          mean that there is a way to use the hosts version of subversion instead of the Jenkins built-in (plug-in whatever) version ?

          No. It just means there's no longer a fork of SVNKit by the Jenkins Project team in use. Subversion plugin does not use the natively installed Subversion client (it doesn't even require one), as it bundles the SVNKit library.

          I don't understand why Jenkins would ever ship with a plug-in installed by default in such a way that's it's not really a plug-in.

          It is. Jenkins works without Subversion Plugin. You can disable it and lose its functionality. It's just bundled and enabled by default for historical reasons (to not break installations upgrading from really ancient versions from before Subversion plugin was detached from core Jenkins – it started life as a part of core Jenkins).

          I also don't understand why there is a separate plug-in that can be a different version from the one shipped by default.

          It's the same plugin, just a newer version of it. Plugins can be updated independently from core versions. The versions of plugins bundled with Jenkins are updated occasionally, but as Subversion 2.0 contained a major, possibly breaking, change to authentication (integration with Credentials plugin) it hasn't been chosen for bundling so far.


          I didn't want to leave your comment unanswered, but please direct any follow-up questions/discussions that aren't directly related to this issue to #jenkins on Freenode, or the jenkinsci-users mailing list. 200 people get an email notification every time you (or anyone) add or edit a comment to this issue.

          Daniel Beck added a comment - mean that there is a way to use the hosts version of subversion instead of the Jenkins built-in (plug-in whatever) version ? No. It just means there's no longer a fork of SVNKit by the Jenkins Project team in use. Subversion plugin does not use the natively installed Subversion client (it doesn't even require one), as it bundles the SVNKit library. I don't understand why Jenkins would ever ship with a plug-in installed by default in such a way that's it's not really a plug-in. It is. Jenkins works without Subversion Plugin. You can disable it and lose its functionality. It's just bundled and enabled by default for historical reasons (to not break installations upgrading from really ancient versions from before Subversion plugin was detached from core Jenkins – it started life as a part of core Jenkins). I also don't understand why there is a separate plug-in that can be a different version from the one shipped by default. It's the same plugin, just a newer version of it. Plugins can be updated independently from core versions. The versions of plugins bundled with Jenkins are updated occasionally, but as Subversion 2.0 contained a major, possibly breaking, change to authentication (integration with Credentials plugin) it hasn't been chosen for bundling so far. I didn't want to leave your comment unanswered, but please direct any follow-up questions/discussions that aren't directly related to this issue to #jenkins on Freenode, or the jenkinsci-users mailing list. 200 people get an email notification every time you (or anyone) add or edit a comment to this issue.

          Andrew Sumner added a comment - - edited

          Is there any reason the the update center in Jenkins doesn't find the 2.5 release? It does find 2.4.5 Running latest LTS Jenkins ver. 1.565.3.

          Andrew Sumner added a comment - - edited Is there any reason the the update center in Jenkins doesn't find the 2.5 release? It does find 2.4.5 Running latest LTS Jenkins ver. 1.565.3.

          Daniel Beck added a comment -

          andrewsumner: 2.5 requires Jenkins 1.568, as you can see on the plugin's wiki page right at the top. 1.565.3 hasn't been "latest LTS" in months, see http://jenkins-ci.org/changelog-stable – the stable update centers just don't offer core upgrades to newer baselines.

          Please ask your next unrelated question on IRC or the jenkinsci-users mailing list. 200 people are notified about every comment created or edited in this issue, so let's keep this on topic (and yes, I realize my comment sends another notification, but I expect that someone would have responded anyway).

          Daniel Beck added a comment - andrewsumner : 2.5 requires Jenkins 1.568, as you can see on the plugin's wiki page right at the top. 1.565.3 hasn't been "latest LTS" in months, see http://jenkins-ci.org/changelog-stable – the stable update centers just don't offer core upgrades to newer baselines. Please ask your next unrelated question on IRC or the jenkinsci-users mailing list. 200 people are notified about every comment created or edited in this issue, so let's keep this on topic (and yes, I realize my comment sends another notification, but I expect that someone would have responded anyway).

          San Jhanjhari added a comment -

          Hi,

          I have got setup Jenkins today with latest version i.e. jenkins-1.611. + SVN 1.8.
          I need to tie up Jenkins to SVN1.8 and seems you could able to do it. Could you please let me know the procedure to install this update to enable SVN 1.8 support?
          I would really appreciate your help on this matter.

          Cheers,
          San

          San Jhanjhari added a comment - Hi, I have got setup Jenkins today with latest version i.e. jenkins-1.611. + SVN 1.8. I need to tie up Jenkins to SVN1.8 and seems you could able to do it. Could you please let me know the procedure to install this update to enable SVN 1.8 support? I would really appreciate your help on this matter. Cheers, San

          Hi, I'm running 1.642.4 and I see the same problem, Subversion 1.8 is not available in the list on Manage Jenkins.
          Any ideas?

          Jonathan Grant added a comment - Hi, I'm running 1.642.4 and I see the same problem, Subversion 1.8 is not available in the list on Manage Jenkins. Any ideas?

          xaviou added a comment -

          Jonathan, which version of Subversion plugin do you have? Make sure you use version 2.5.5 at least.

          xaviou added a comment - Jonathan, which version of Subversion plugin do you have? Make sure you use version 2.5.5 at least.

          Hello Xaviou
          My 1.642.4 came with Subversion plugin 1.54

          I'll install it.

          I can see Jenkins site has 2.5.7 for download. Do you know if there is a reason this isn't included with Jenkins standard full installation?

          Jonathan Grant added a comment - Hello Xaviou My 1.642.4 came with Subversion plugin 1.54 I'll install it. I can see Jenkins site has 2.5.7 for download. Do you know if there is a reason this isn't included with Jenkins standard full installation?

          John Tal added a comment - - edited

          This issue occurs in RHEL 5.11 with Jenkins 2.5 and the SVN plugin 2.5.7.
          Base svn installed on RHEL is svn, version 1.8.15 (r1718365)
          [ERROR] The svn command failed.
          [ERROR] Command output:
          [ERROR] svn: E155036: Please see the 'svn upgrade' command
          svn: E155036: The working copy at '/snipped'
          is too old (format 8) to work with client version '1.8.15 (r1718365)' (expects format 31). You need to upgrade the working copy first.

          This issue resolved by Manage Jenkins -> Configure system -> Subversion Workspace Version update from the default of 1.4 to 1.8 (seems like at least 1.7 should be default)

          John Tal added a comment - - edited This issue occurs in RHEL 5.11 with Jenkins 2.5 and the SVN plugin 2.5.7. Base svn installed on RHEL is svn, version 1.8.15 (r1718365) [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E155036: Please see the 'svn upgrade' command svn: E155036: The working copy at '/snipped' is too old (format 8) to work with client version '1.8.15 (r1718365)' (expects format 31). You need to upgrade the working copy first. This issue resolved by Manage Jenkins -> Configure system -> Subversion Workspace Version update from the default of 1.4 to 1.8 (seems like at least 1.7 should be default)

            schristou Steven Christou
            mmlegra Matt Legrand
            Votes:
            178 Vote for this issue
            Watchers:
            192 Start watching this issue

              Created:
              Updated:
              Resolved: