SCM build trigger not working correctly with variables in SVN URL

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      I tried using variables in my SVN URL with Subversion plug-in 1.29, but now the SCM build trigger triggers a new build on every update check.

      I created two global variables in the Jenkins System Configuration:

      MYSVN_BASE=file:///home/svn/myproject
      MYSVN_BRANCH=trunk

      and in my build job I use

      $MYSVN_BASE/$MYSVN_BRANCH

      as the SVN URL and the SCM build trigger set to check every 15 minutes for updates.

      Despite a nasty "Invalid URL syntax" error marker below the URL field, checking out and building the project works fine. However, the log says:

      Started by an SCM change
      Updating file:///home/svn/myproject/trunk
      At revision 13360
      no revision recorded for $MYSVN_BASE/$MYSVN_BRANCH in the previous build

      And on any subsequent SCM check, the build is triggered with that same message...

        1. JENKINS-10628.patch
          2 kB
        2. subversion-plugin-1.43-Jenkins-16116.patch
          1.81 MB

            Assignee:
            sogabe
            Reporter:
            Carsten Reckord
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: