Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17974

SVN plugin always overwrites --depth parameters

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      As we have a huge SVN repository, a selective svn checkout is done to minimize the checkout and update times during the build.

      First set all subfolders to be excluded:
      svn co http://reposerver/repos/project/trunk source --depth immediates
      svn update --set-depth exclude source\Folder1
      svn update --set-depth exclude source\Folder2
      svn update --set-depth exclude source\Folder3

      Then the needed subfolders are included again:
      svn update --set-depth infinity source\Folder2

      The expected behavior is to update only the included folder on an "svn up".

      The SVN plugin does not allow to update without --depth attribute. Because of this it is not possible to update depending on the workspace settings (which are mixed: immediates and infinity) but only on the possible settings in the SVN plugin (which are: infinity, empty, files, immediates)

        Attachments

          Activity

          Hide
          ascheucher Andreas Scheucher added a comment -

          The problem could be solved with an an additional option repository depth: none

          Show
          ascheucher Andreas Scheucher added a comment - The problem could be solved with an an additional option repository depth: none
          Hide
          slawomir_czarko Slawomir Czarko added a comment -

          Is the component here correct? I'm working on a fix for this issue but for subversion-plugin not for svncompat13.

          Show
          slawomir_czarko Slawomir Czarko added a comment - Is the component here correct? I'm working on a fix for this issue but for subversion-plugin not for svncompat13.
          Hide
          ascheucher Andreas Scheucher added a comment -

          I am not sure about the component anymore. But AFAIK it was the only one related to SVN, hence I choose it. I guess it's wrong.

          Show
          ascheucher Andreas Scheucher added a comment - I am not sure about the component anymore. But AFAIK it was the only one related to SVN, hence I choose it. I guess it's wrong.
          Hide
          slawomir_czarko Slawomir Czarko added a comment -

          Which SVN version are you using?

          Show
          slawomir_czarko Slawomir Czarko added a comment - Which SVN version are you using?
          Hide
          kutzi kutzi added a comment - - edited

          So, actually it doesn't 'ignore' the depth option, but overwrites it in any case, right?

          I'm not terribly in favor of this feature as it basically sounds to me like you are working around the fact that your SVN repository is not organised optimally.
          However, since this would - according to the pull request (https://github.com/jenkinsci/subversion-plugin/pull/46) - only require a single new value in an existing drop-down menu, I could live with it.

          Show
          kutzi kutzi added a comment - - edited So, actually it doesn't 'ignore' the depth option, but overwrites it in any case, right? I'm not terribly in favor of this feature as it basically sounds to me like you are working around the fact that your SVN repository is not organised optimally. However, since this would - according to the pull request ( https://github.com/jenkinsci/subversion-plugin/pull/46 ) - only require a single new value in an existing drop-down menu, I could live with it.
          Hide
          ascheucher Andreas Scheucher added a comment -

          At time of posting the issue, it was 1.7. Currently 1.8.

          Yes, it seems to be overwritten. If one does an "svn up" on the command line, svn behaves the excpected way (,like configured during checkout). If it's done with the jenkins job configuration, it behaves like set in the drop-down, ignoring the set values.

          For sure, I was working around a not optimally set up SVN repository. But I am sure, this will happen to a lot of other users as well. Especially, if you need to set up continuous delivery for legacy projects, with a lot of svn:externals and not optimal repository structure. I am talking of several GB of source and configuration, which was fetched in my case and times of weeks for first attempts in reorganising the repository, to get better separation.

          Show
          ascheucher Andreas Scheucher added a comment - At time of posting the issue, it was 1.7. Currently 1.8. Yes, it seems to be overwritten. If one does an "svn up" on the command line, svn behaves the excpected way (,like configured during checkout). If it's done with the jenkins job configuration, it behaves like set in the drop-down, ignoring the set values. For sure, I was working around a not optimally set up SVN repository. But I am sure, this will happen to a lot of other users as well. Especially, if you need to set up continuous delivery for legacy projects, with a lot of svn:externals and not optimal repository structure. I am talking of several GB of source and configuration, which was fetched in my case and times of weeks for first attempts in reorganising the repository, to get better separation.
          Hide
          ascheucher Andreas Scheucher added a comment -

          thanks for you effort!

          Show
          ascheucher Andreas Scheucher added a comment - thanks for you effort!

            People

            • Assignee:
              kutzi kutzi
              Reporter:
              ascheucher Andreas Scheucher
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: