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

Subversion SCM Polling fails when using parameterized Repository URL

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Duplicate
    • Component/s: subversion-plugin
    • Labels:
      None
    • Environment:
      windows 2003 server, Jenkins 1.421, Subversion Plugin 1.2.8

      Description

      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.

        Issue Links

          Activity

          erezul Erez Harari created issue -
          erezul Erez Harari made changes -
          Field Original Value New Value
          Environment windows 2003 server windows 2003 server, Jenkins 1.421, Subversion Plugin 1.2.8
          Description 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 SVN_REVISION environment variable is not set.
          When using a clear text Repository URL all works fine.
          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 ${ECHOS_SVN_URL}/echos-ws. Need a new build.
          Done. Took 0 ms
          Changes found

          When using a clear text Repository URL all works fine.
          erezul Erez Harari made changes -
          Description 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 ${ECHOS_SVN_URL}/echos-ws. Need a new build.
          Done. Took 0 ms
          Changes found

          When using a clear text Repository URL all works fine.
          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.
          kutzi kutzi made changes -
          Link This issue duplicates JENKINS-10628 [ JENKINS-10628 ]
          kutzi kutzi made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Duplicate [ 3 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              erezul Erez Harari
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: