• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Platform: All, OS: All

      It could be useful to have support for non recursive checkout/update.

          [JENKINS-1311] Support for non-recursive checkout/update

          mdonohue added a comment -
              • Issue 1922 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 1922 has been marked as a duplicate of this issue. ***

          mdonohue added a comment -

          issue 1922 has a more verbose description of this feature

          mdonohue added a comment - issue 1922 has a more verbose description of this feature

          pascalra added a comment -

          Created an attachment (id=915)
          This SVN patch file (subversion-1.7-non-recursive-checkout.patch) has been made based on the Hudson Subversion plug-in version "1.7". It allows for each job to configure if the subversion checkout/update has to be done recursively or not. The job configuration web page, in the "Subversion" part of the "Source Code Management" section, presents a new "Recursive" check box that is checked by default. If the user unchecks this "Recursive" option, then the subversion checkout/update of the source code will be done non-recursively.

          pascalra added a comment - Created an attachment (id=915) This SVN patch file (subversion-1.7-non-recursive-checkout.patch) has been made based on the Hudson Subversion plug-in version "1.7". It allows for each job to configure if the subversion checkout/update has to be done recursively or not. The job configuration web page, in the "Subversion" part of the "Source Code Management" section, presents a new "Recursive" check box that is checked by default. If the user unchecks this "Recursive" option, then the subversion checkout/update of the source code will be done non-recursively.

          mdp added a comment -

          I'm afraid that one switch per job will not be very useful. The motivating use
          case described in issue 1922 (and I have a very similar case) would seem to
          require a non-recursive checkout of the top-level directory and recursive
          checkouts of some subdirectories used by the job. So a setting per checked-out
          module would be the appropriate granularity.

          mdp added a comment - I'm afraid that one switch per job will not be very useful. The motivating use case described in issue 1922 (and I have a very similar case) would seem to require a non-recursive checkout of the top-level directory and recursive checkouts of some subdirectories used by the job. So a setting per checked-out module would be the appropriate granularity.

          pascalra added a comment -

          Created an attachment (id=1042)
          This SVN patch file (subversion-1.7-non-recursive-checkout-per-modules.patch) has been made based on the Hudson Subversion plug-in version "1.7". It allows for each SCM modules within a job to configure if the subversion checkout/update has to be done recursively or not. The job configuration web page, in the "Subversion" part of the "Source Code Management" section, presents a new "Recursive" check box that is checked by default. If the user unchecks this "Recursive" option, then the subversion checkout/update of the source code will be done non-recursively.

          pascalra added a comment - Created an attachment (id=1042) This SVN patch file (subversion-1.7-non-recursive-checkout-per-modules.patch) has been made based on the Hudson Subversion plug-in version "1.7". It allows for each SCM modules within a job to configure if the subversion checkout/update has to be done recursively or not. The job configuration web page, in the "Subversion" part of the "Source Code Management" section, presents a new "Recursive" check box that is checked by default. If the user unchecks this "Recursive" option, then the subversion checkout/update of the source code will be done non-recursively.

          pascalra added a comment -

          Hello,
          The second version of the patch that I submitted the 25/Nov/2009 allows to define the recursive option per checked-out module. Did you have time to check it? Does it fulfil your requirement? Will it be integrated into the future release?
          Thank you in advance for your answers.
          Best regards.

          pascalra added a comment - Hello, The second version of the patch that I submitted the 25/Nov/2009 allows to define the recursive option per checked-out module. Did you have time to check it? Does it fulfil your requirement? Will it be integrated into the future release? Thank you in advance for your answers. Best regards.

          Aaron Laws added a comment -

          So, how do we get that patch integrated into the next release?

          Aaron Laws added a comment - So, how do we get that patch integrated into the next release?

          Aaron Laws added a comment -

          Assigning to pascalra. He seems to have fixed the problem.

          Aaron Laws added a comment - Assigning to pascalra. He seems to have fixed the problem.

            pascalra pascalra
            canhuth canhuth
            Votes:
            11 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: