[JENKINS-21943] Parameterised Subversion revision should apply to subdirectories as well as the working copy root

We were trying to configure Jenkins to trigger one build from another, carrying the same Subversion revision over into the new build. I couldn't get this to work using the Parameterized Trigger plugin so I eventually filed a ticket about that (JENKINS-21586">JENKINS-21586) because it wasn't doing what it said it would, but they said that this is a limitation in the Subversion plugin.

Essentially, the Parameterized Trigger plugin is triggering a build and telling the Subversion plugin to use a specific revision for the URL when it checks it out.

What I expect to happen is for both checkouts to use the revision which was passed in.

What actually happens is that the root directory uses the revision which was passed in and the subdirectory is checked out from HEAD.

---
Originally reported by trejkaz, imported from: Parameterised Subversion revision should apply to subdirectories as well as the working copy root

• status: Open
  
• priority: Major
  
• component(s): subversion-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251212-090250
  

Raw content of original issue

We were trying to configure Jenkins to trigger one build from another, carrying the same Subversion revision over into the new build. I couldn't get this to work using the Parameterized Trigger plugin so I eventually filed a ticket about that (JENKINS-21586) because it wasn't doing what it said it would, but they said that this is a limitation in the Subversion plugin.


Essentially, the Parameterized Trigger plugin is triggering a build and telling the Subversion plugin to use a specific revision for the URL when it checks it out.


What I expect to happen is for both checkouts to use the revision which was passed in.


What actually happens is that the root directory uses the revision which was passed in and the subdirectory is checked out from HEAD.