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

Subversion SCM Polling fails when using parameterized Repository URL

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • subversion-plugin
    • None
    • windows 2003 server, Jenkins 1.421, Subversion Plugin 1.2.8

      I'm using a single Repository URL with parameterized value: ${SVN_URL}/application, where SVN_URL is defined as a node level parameter. in that case SCM polling keeps running and chackout the entire workspace although there are no changes on SVN.

      scm-polling.log:
      Workspace doesn't contain ${SVN_URL}/application. Need a new build.
      Done. Took 0 ms
      Changes found

      When using a clear text Repository URL all works fine.

          [JENKINS-10485] Subversion SCM Polling fails when using parameterized Repository URL

          kutzi added a comment -

          I assume this is a dup of JENKINS-10628

          If not please reopen with details about how this is different from the other issue

          kutzi added a comment - I assume this is a dup of JENKINS-10628 If not please reopen with details about how this is different from the other issue

          mesa added a comment -

          After I've stumbled upon this problem, I've updated to Jenkins 2.361.1 and Subversion plugin 2.16.0, but it's still here. Therefore, I want to re-open this issue, as it doesn't seem solved to me.

          My scenario:

          I've configured a parameter variable in my Jenkins job with a Jenkinsfile from an SVN url. When the job is run manually, everything works, and the variable will be subtituted by its value. But polling doesn't work because the variable is not substituted, and thus an SCM change is detected in each poll - exactly as described earlier in this issue.

          mesa added a comment - After I've stumbled upon this problem, I've updated to Jenkins 2.361.1 and Subversion plugin 2.16.0, but it's still here. Therefore, I want to re-open this issue, as it doesn't seem solved to me. My scenario: I've configured a parameter variable in my Jenkins job with a Jenkinsfile from an SVN url. When the job is run manually, everything works, and the variable will be subtituted by its value. But polling doesn't work because the variable is not substituted, and thus an SCM change is detected in each poll - exactly as described earlier in this issue.

            Unassigned Unassigned
            erezul Erez Harari
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: