Subversion SCM Polling fails when using parameterized Repository URL

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

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            Erez Harari
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: