[JENKINS-25273] [Feature] Exclude Directories from Checkout using sparse checkout

Problem:

On big svn it is not possible to exclude directories from checkout / update.

Feature:

A field "exclude checkout" has to be added to ModuleLocation.

In this field relative paths (base path is svn url) can be defined,

which will be excluded from checkout / update of a workspace.

The delimiter of multiple directories are ';'.

The folder separator is '/'.

Example: "subfolder/subfolder;foo/bar"

Solution:

Find attached our changes to the svnplugin.

This first approach seems to be working well.

But where is a problem with the method "finish()"

in hudson.scm.SubversionChangeLogSet.

We get errors in the sorting routine. Our quick and dirty solution was to deactivate the sorting, but we don't know possible dependencies to other functionality.

It would be nice if this or a similar function can be integrated in one of the next releases of the subversion plugin.

Best regards

Daniel

---
Originally reported by daniel727, imported from: [Feature] Exclude Directories from Checkout using sparse checkout

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

Raw content of original issue

Problem:

On big svn it is not possible to exclude directories from checkout / update.


Feature:

A field "exclude checkout" has to be added to ModuleLocation.

In this field relative paths (base path is svn url) can be defined,

which will be excluded from checkout / update of a workspace.

The delimiter of multiple directories are ';'.

The folder separator is '/'.


Example: "subfolder/subfolder;foo/bar"


Solution:

Find attached our changes to the svnplugin.

This first approach seems to be working well.


But where is a problem with the method "finish()"

in hudson.scm.SubversionChangeLogSet.

We get errors in the sorting routine. Our quick and dirty solution was to deactivate the sorting, but we don't know possible dependencies to other functionality.


It would be nice if this or a similar function can be integrated in one of the next releases of the subversion plugin.


Best regards


Daniel

2 attachments

- [subversion-plugin-master.zip](https://issues.jenkins.io/secure/attachment/27829/subversion-plugin-master.zip)
- [subversion.hpi](https://issues.jenkins.io/secure/attachment/27835/subversion.hpi)