[JENKINS-5298] Consistent checkout version across svn modules, including with externals

Consider a job that asks for several subversion modules from the same repo. If the svn server is pokey, or some of them are big, or both, it's possible to get 'skewed' – to get different revs of different modules. It would be handy if the svn support would notice, or could be told, that a set of modules are from one server, and that a consistent rev is desirable.

It would also be helpful if a directory with externals is used to pull in a set of modules if the same consistency treatment could be arranged.

---
Originally reported by bimargulies, imported from: Consistent checkout version across svn modules, including with externals

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

Raw content of original issue

Consider a job that asks for several subversion modules from the same repo. If the svn server is pokey, or some of them are big, or both, it's possible to get 'skewed' – to get different revs of different modules. It would be handy if the svn support would notice, or could be told, that a set of modules are from one server, and that a consistent rev is desirable.


It would also be helpful if a directory with externals is used to pull in a set of modules if the same consistency treatment could be arranged.