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

Local module directory contains @NNN when @NNN is used in Subversion repository URL.

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      If the local module directory is not specified, then the @NNN is
      included in the module name. For example, when I specify
      svn://hood/svnroot/product/trunk/buildtools@HEAD, the result is
      a directory buildtools@HEAD, as opposed to buildtools, as I'd
      expect.

      The workaround is to always specify the local module directory.

      Jenkins v1.425, Subversion plugin v1.31

        Attachments

          Activity

          Hide
          sogabe sogabe added a comment -

          Integrated in plugins_subversion #106
          [FIXED JENKINS-10943] Local module directory contains @NNN when @NNN is used in Subversion repository URL.

          sogabe :
          Files :

          /trunk/hudson/plugins/subversion/src/main/java/hudson/scm/SubversionSCM.java
          /trunk/hudson/plugins/subversion/src/test/java/hudson/scm/SubversionSCMTest.java

          Show
          sogabe sogabe added a comment - Integrated in plugins_subversion #106 [FIXED JENKINS-10943] Local module directory contains @NNN when @NNN is used in Subversion repository URL. sogabe : Files : /trunk/hudson/plugins/subversion/src/main/java/hudson/scm/SubversionSCM.java /trunk/hudson/plugins/subversion/src/test/java/hudson/scm/SubversionSCMTest.java
          Hide
          ebann ebann added a comment - - edited

          I'm seeing this issue in Jenkins ver. 1.430 and subversion 1.32
          Is it normal ? (I can't find a release version for this fix)

          I have something like:
          svn://hood/svnroot/product/SignalProc@$mysvnrevision

          And I launch my Job with mysvnrevision=54321

          And the local module directory created automaticaly is:
          SignalProcessing@54321

          And worst, this variable replacement is not done for ANT build step:
          FATAL: Unable to find build script at /tmp/jenkins_slave/workspace/SignalProc/SignalProc@$svnrevision/build.xml

          Show
          ebann ebann added a comment - - edited I'm seeing this issue in Jenkins ver. 1.430 and subversion 1.32 Is it normal ? (I can't find a release version for this fix) I have something like: svn://hood/svnroot/product/SignalProc@$mysvnrevision And I launch my Job with mysvnrevision=54321 And the local module directory created automaticaly is: SignalProcessing@54321 And worst, this variable replacement is not done for ANT build step: FATAL: Unable to find build script at /tmp/jenkins_slave/workspace/SignalProc/SignalProc@$svnrevision/build.xml
          Hide
          sogabe sogabe added a comment -

          >I'm seeing this issue in Jenkins ver. 1.430 and subversion 1.32
          >Is it normal ? (I can't find a release version for this fix)
          yes, See changelog https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin#SubversionPlugin-Version1.32%28Sep15%2C2011%29

          >And I launch my Job with mysvnrevision=54321
          >And the local module directory created automaticaly is:
          >SignalProcessing@54321

          How did you pass $mysvnrevision valiable to job? build parameter or enviroment variable?

          Show
          sogabe sogabe added a comment - >I'm seeing this issue in Jenkins ver. 1.430 and subversion 1.32 >Is it normal ? (I can't find a release version for this fix) yes, See changelog https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin#SubversionPlugin-Version1.32%28Sep15%2C2011%29 >And I launch my Job with mysvnrevision=54321 >And the local module directory created automaticaly is: >SignalProcessing@54321 How did you pass $mysvnrevision valiable to job? build parameter or enviroment variable?
          Hide
          kutzi kutzi added a comment -

          according to sogabe's commit this should be fixed in 1.32+.
          Please reopen, if this is still an issue

          Show
          kutzi kutzi added a comment - according to sogabe's commit this should be fixed in 1.32+. Please reopen, if this is still an issue

            People

            • Assignee:
              sogabe sogabe
              Reporter:
              ammon Ammon Riley
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: