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

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.

---
Originally reported by erezul, imported from: Subversion SCM Polling fails when using parameterized Repository URL

• status: Reopened
  
• priority: Critical
  
• component(s): subversion-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 2
  
• imported: 20251212-090250
  

Raw content of original issue

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.

• environment: windows 2003 server, Jenkins 1.421, Subversion Plugin 1.2.8