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

Add Local module directory field like Subversion plugin

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • filesystem_scm-plugin
    • None
    • All

      It would be really useful to have a Local module directory for this plugin that works the same way as it does for the Subversion plugin

          [JENKINS-15496] Add Local module directory field like Subversion plugin

          samngms added a comment -

          Please see if my understanding is correct.

          For example, if the source directory is "c:\project1\component1\folder1", it may checkout to path "C:\xx\yy\"

          If the "local_module_directory" is "folder2", then it will checkout to path "c:\xx\yy\folder2", am I correct?

          If the "local_module_directory" is undefined, then it will checkout to path "c:\xx\yy\folder1", am I correct?

          If the "local_module_directory" is ".", then it will checkout to path "c:\xx\yy", same as before, am I correct?

          But for backward compatibility, I think I would change the implementation to if "local_module_directory" is not defined, it will just checkout to "c:\xx\yy" (same as ".")

          samngms added a comment - Please see if my understanding is correct. For example, if the source directory is "c:\project1\component1\folder1", it may checkout to path "C:\xx\yy\" If the "local_module_directory" is "folder2", then it will checkout to path "c:\xx\yy\folder2", am I correct? If the "local_module_directory" is undefined, then it will checkout to path "c:\xx\yy\folder1", am I correct? If the "local_module_directory" is ".", then it will checkout to path "c:\xx\yy", same as before, am I correct? But for backward compatibility, I think I would change the implementation to if "local_module_directory" is not defined, it will just checkout to "c:\xx\yy" (same as ".")

          Andrew Gray added a comment -

          Hi Samngms,

          I think you are largely correct

          As with the svn plugin the local_module_directory field should be set to "." by default

          If the "local_module_directory" is "." or empty the source directory should be "checked out" (i.e. copied) to C:\<JenkinsInstallLocation>\workspace\<jobname>

          If the "local_module_directory" is "folder2", the source directory should be "checked out" (i.e. copied) to C:\<JenkinsInstallLocation>\workspace\<jobname>\folder2

          Hope this helps.

          Regards,

          Andrew

          Andrew Gray added a comment - Hi Samngms, I think you are largely correct As with the svn plugin the local_module_directory field should be set to "." by default If the "local_module_directory" is "." or empty the source directory should be "checked out" (i.e. copied) to C:\<JenkinsInstallLocation>\workspace\<jobname> If the "local_module_directory" is "folder2", the source directory should be "checked out" (i.e. copied) to C:\<JenkinsInstallLocation>\workspace\<jobname>\folder2 Hope this helps. Regards, Andrew

          Ernst de Haan added a comment -

          If and when this is implemented, seems like it would benefit from some unit tests, to cover the different cases properly.

          Ernst de Haan added a comment - If and when this is implemented, seems like it would benefit from some unit tests, to cover the different cases properly.

            samngms samngms
            apgray Andrew Gray
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: