Something is triggering your Jenkins job - you poll your SVN repository or you have a SVN trigger as descriped here.
In both ways you start your job with a configured
- Source-Code-Management: Subversion
- Check-out Strategy: use 'svn update' as much as possible
Then you start your Groovy system script:
import hudson.model.*
import hudson.util.*
import hudson.scm.*
// work with current build
// (does only work as groovy system script, not in the Jenkins shell)
def build = Thread.currentThread()?.executable
// for testing, comment the line above and uncomment the job line
// and one of the build lines - use specific build (last build or build by number)
//def job = hudson.model.Hudson.instance.getItem("<your job name>")
//def build = job.getLastBuild()
//def build = job.getBuildByNumber(162)
// get ChangesSets with all changed items
def changeSet= build.getChangeSet()
def items = changeSet.getItems()
But at this stage the files are already on your build machine! The changeSet contains all items which have been in the svn update. So just use the path to process them. For example you could start a Jenkins job per changed file with:
void startJenkinsJob(jobName, param)
{
// Start another job
def job = Hudson.instance.getJob(jobName)
def anotherBuild
try {
def params = [
new StringParameterValue('StringParam', param),
]
def future = job.scheduleBuild2(0, new Cause.UpstreamCause(build), new ParametersAction(params))
println "Waiting for the completion of " + HyperlinkNote.encodeTo('/' + job.url, job.fullDisplayName)
anotherBuild = future.get()
} catch (CancellationException x) {
throw new AbortException("${job.fullDisplayName} aborted.")
}
println HyperlinkNote.encodeTo('/' + anotherBuild.url, anotherBuild.fullDisplayName) + " completed. Result was " + anotherBuild.result
// Check that it succeeded
build.result = anotherBuild.result
if (anotherBuild.result != SUCCESS && anotherBuild.result != UNSTABLE) {
// We abort this build right here and now.
throw new AbortException("${anotherBuild.fullDisplayName} failed.")
}
}