I reviewed some of the source code of both sventon and the subversion plugin for Jenkins. Two things I noticed.
http://grepcode.com/file/repo1.maven.org/maven2/org.jvnet.hudson.plugins/subversion/1.16/hudson/scm/browsers/Sventon2.java return new URL(url, String.format("repos/%s/diff/%s?revision=%d", encodePath(repositoryInstance),encodePath(getPath(path)), r)); The sventon 2.x compatibility in the subversion plugin for Jenkins does properly account for the repository. In this case the Repository Instance is the repository name in sventon. The second thing I've found is that sventon can only check out repository roots. In Jenkins, I was checking out a repository path. e.g.: svn+ssh://someserver/rootRepo/path/to/folder However sventon was not able to process the /path/to/folder and only rendered the following URL in the repository listing. svn+ssh://someserver/rootRepo That's not Jenkins problem but sventon. Once I learned that I tried checking out the full repository just for kicks in Jenkins so that they would match up to be the same in the Jenkins workspace and in sventon. This did not change anything. I don't know what is supposed to happen upon successful "integration" yet but nothing happens right now. SAM
