Jenkins: How to use SVN Checkout Strategies with Multibranch pipelines

Recently, we had the problem that we moved large SVN repositories to Jenkins multibranch pipelines.

There, a typical checkout looks like this:

	node {
	deleteDir()
	checkout scm
	}

view raw Jenkinsfile-svn-strategy1.groovy hosted with ❤ by GitHub

Here, the issue is that there is always a fresh checkout performed. This can take a very long time for larger repositories. The SVN Multibranch pipeline lacks the possibility to define the checkout strategy that could be definen in the old way, or when working with simple pipeline scripts.

The solution is to manipulate the scm object, that is present in the multibranch pipeline:

	import hudson.scm.subversion.UpdateWithCleanUpdater
	node {
	def scmClone = scm
	scmClone.setWorkspaceUpdater( new UpdateWithCleanUpdater())
	//scmClone.setWorkspaceUpdater( new UpdateUpdater())
	//scmClone.setWorkspaceUpdater( new UpdateWithRevertUpdater())
	checkout scmClone
	}

view raw Jenkinsfile-svn-strategy2.groovy hosted with ❤ by GitHub

You can also do other things with the scm object, for example make the output quiet:

	import hudson.scm.subversion.UpdateWithCleanUpdater
	node {
	def scmClone = scm
	scmClone.setWorkspaceUpdater( new UpdateWithCleanUpdater())
	scmClone.quietOperation = true
	checkout scmClone
	}

view raw Jenkinsfile-svn-strategy3.groovy hosted with ❤ by GitHub