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

          Erez Harari created issue -
          Erez Harari made changes -
          Description Original: 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.
          New: 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.
          Environment Original: windows 2003 server New: windows 2003 server, Jenkins 1.421, Subversion Plugin 1.2.8
          Erez Harari made changes -
          Description Original: 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.
          New: 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 made changes -
          Link New: This issue duplicates JENKINS-10628 [ JENKINS-10628 ]
          kutzi made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 140678 ] New: JNJira + In-Review [ 189190 ]
          mesa made changes -
          Resolution Original: Duplicate [ 3 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

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

              Created:
              Updated: