[JENKINS-1304] Add a "Use Export" option to the Subversion config section of a job

It would be great to have a "Use Export" option on the Subversion configuration

section of a job, similar to the current "Use Update" option.

This greatly speeds up the checkout time for a build.

The feature is applicable when:

1. Your project does not have a reliable clean or rebuild setup, or you

absolutely want to start with a clean workspace for every build.

2. You project does not expect to perform any working copy subversion

operations as part of the build.

We made a quick hack to test the approach by changing the source to use

"checkout" for only the root module directory (no recursion), and then "export"

the module with full recursion. The change dropped our checkout time from 31 to

11 minutes. The approach we coded was not very clean. It would probably be

better to run only the "export" command and use the returned revision number to

obtain the necessary SVNInfo object from the server instead of the working copy

(for change log and tagging purposes).

---
Originally reported by avanha, imported from: Add a "Use Export" option to the Subversion config section of a job

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

Raw content of original issue

It would be great to have a "Use Export" option on the Subversion configuration

section of a job, similar to the current "Use Update" option.  

This greatly speeds up the checkout time for a build.


The feature is applicable when:

1.  Your project does not have a reliable clean or rebuild setup, or you

absolutely want to start with a clean workspace for every build.

2.  You project does not expect to perform any working copy subversion

operations as part of the build.


We made a quick hack to test the approach by changing the source to use

"checkout" for only the root module directory (no recursion), and then "export"

the module with full recursion.  The change dropped our checkout time from 31 to

  11 minutes.  The approach we coded was not very clean.  It would probably be

better to run only the "export" command and use the returned revision number to

obtain the necessary SVNInfo object from the server instead of the working copy

(for change log and tagging purposes).

• environment: Platform: All, OS: All