• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None

      Currently it seems that SVN checkout version can be only set as part of the global settings, however when more than one nodes are being used, the build slaves can end up using different SVN versions quite easily (personally I'm suffering from the SVN 1.6 <-> 1.7 incompatibilities), so it is possible to actually check out in 1.7 format on a slave, where locally only 1.6 is available and then build scripts are failing to execute SVN commands (i.e. through Makefiles). It should be possible to either set checkout version on a slave basis, or maybe even per build job.

          [JENKINS-19714] Make SVN checkout version a less global setting

          I'm facing the same problem here. It seems to me that a per node configuration, overriding the global one, would be perfect.

          Gustavo Chaves added a comment - I'm facing the same problem here. It seems to me that a per node configuration, overriding the global one, would be perfect.

          Matt Legrand added a comment -

          Same here. We have a slave farm with different Linux OS flavors and versions (and thus different svn versions). SVN working folders are not compatible between the svn versions.

          A workaround (in the build script) would be to do "svn upgrade", if one has SVN 1.7.* installed and is using SVN 1.6.* in Jenkins. This lets one do further svn operations on the repo that was checked out by the Jenkins svn plugin. But this is a kludge.

          Matt Legrand added a comment - Same here. We have a slave farm with different Linux OS flavors and versions (and thus different svn versions). SVN working folders are not compatible between the svn versions. A workaround (in the build script) would be to do "svn upgrade", if one has SVN 1.7.* installed and is using SVN 1.6.* in Jenkins. This lets one do further svn operations on the repo that was checked out by the Jenkins svn plugin. But this is a kludge.

          aldaris added a comment -

          Looks like JENKINS-14157 and JENKINS-14690 already covers these problems, I'm resolving this issue as duplicate.

          aldaris added a comment - Looks like JENKINS-14157 and JENKINS-14690 already covers these problems, I'm resolving this issue as duplicate.

          Is it currently part of the product? I use a 2019 version of Jenkins and am still forced to switch of GLOBAL svn settings while switching of jobs (if needed).

          What is the status of this feature? Is it well documented?

          Germain Barret added a comment - Is it currently part of the product? I use a 2019 version of Jenkins and am still forced to switch of GLOBAL svn settings while switching of jobs (if needed). What is the status of this feature? Is it well documented?

          Germain Barret added a comment - - edited

          This problem is still there.
          Why is it closed?
          Is there a workaround?

           

          ...Cover, but don't solve it...

          Germain Barret added a comment - - edited This problem is still there. Why is it closed? Is there a workaround?   ...Cover, but don't solve it...

            aldaris aldaris
            aldaris aldaris
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: