[JENKINS-9706] release variables cannot affect SVN repository path

In a parameterized job, we use the build parameter SVN_PATH to set part of the SVN repository path that is checked out. This allows us to build different SVN branches in the same job.

However this does not work for release builds, if SVN_PATH is a release variable instead. The value somehow does not take effect, and it keeps using the default value for the SVN_PATH build parameter instead. (This is the opposite of what happens during the build steps, where release vars override equally named build parameters).

---
Originally reported by mbetter, imported from: release variables cannot affect SVN repository path

• assignee: petehayes
  
• status: Open
  
• priority: Major
  
• component(s): release-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 1
  
• imported: 20251223-222157
  

Raw content of original issue

In a parameterized job, we use the build parameter SVN_PATH to set part of the SVN repository path that is checked out. This allows us to build different SVN branches in the same job.


However this does not work for release builds, if SVN_PATH is a release variable instead. The value somehow does not take effect, and it keeps using the default value for the SVN_PATH build parameter instead. (This is the opposite of what happens during the build steps, where release vars override equally named build parameters).

• environment: Jenkins 1.408, Release plugin 2.1