[JENKINS-39064] SVN checkout may result in mixed revisions when using externals

We are using a rather complex SVN structure for our software projects with many externals. Since checkout of externals is rather slow, it happens regularly to us, that a commit is performed to the repository, while the checkout is still running. Unfortunately this causes the externals to be checked out with different (head) revisions - resulting into a "mixed source" warning of our build script later.

Is there any way check out a SVN project with a consistent head revision for all externals?

Is it possible to let the SVN plugin repeat a checkout when a "mixed source" condition is detected?

---
Originally reported by rstahn, imported from: SVN checkout may result in mixed revisions when using externals

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

Raw content of original issue

We are using a rather complex SVN structure for our software projects with many externals. Since checkout of externals is rather slow, it happens regularly to us, that a commit is performed to the repository, while the checkout is still running. Unfortunately this causes the externals to be checked out with different (head) revisions - resulting into a "mixed source" warning of our build script later.


Is there any way check out a SVN project with a consistent head revision for all externals?

Is it possible to let the SVN plugin repeat a checkout when a "mixed source" condition is detected?

environment

```
Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06)

subversion@2.6
```