[JENKINS-10222] Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)

I am using a SVN repository which is being checked out at the beginning of every build in a Jenkins job. It is set to "poll SCM" for updates. However, regardless of whether there were changes or not it is cleaning out the workspace and downloading the whole repository in it's entirety every time which is unnecessary.

Builds are taking much longer than they should as the SVN poll should only be checking out newly-updated files. Sample log:

Checking out a fresh workspace because the workspace is not file://PICKLE/Repositories/project

Cleaning workspace.....

---
Originally reported by giles, imported from: Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)

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

Raw content of original issue

I am using a SVN repository which is being checked out at the beginning of every build in a Jenkins job. It is set to "poll SCM" for updates. However, regardless of whether there were changes or not it is cleaning out the workspace and downloading the whole repository in it's entirety every time which is unnecessary.


Builds are taking much longer than they should as the SVN poll should only be checking out newly-updated files. Sample log:


Checking out a fresh workspace because the workspace is not file://PICKLE/Repositories/project

Cleaning workspace.....

• environment: Windows