Hi Everyone,
I have (unfortunately) no java skills to assist with a solution.
But please let me add my +1 to the requirement to support SVN 1.7
We have recently upgraded SVN to 1.7
(It solves a few major issues we had with 1.6)

And subsequently cannot use Jenkins for checking out / updating our code.
We are able to do this via ANT, but it is slightly painful.

Gavin.

This is a critical bug. I just updated my subversion installation, and it broke Jenkins. I can't downgrade svn at this time.

Jenkins uses SVNKit internally for subversion support. Until SVNKit doesn't support 1.7 - announced for end of November http://svnkit.com/download.php - I'm afraid there isn't much we can do about it.

Thank you for the update kutzi.

Does anyone know a workaround, even temporary/unstable one? I tried finding the unstable svnkit jars, but could not find them. Before I spend the time figuring out how to build it, I am curious, would simply replacing the Jenkins svnkit jars be a possible workaround?

Is there a possibility of using JavaHL with Jenkins svn plugin?

P.S. Thanks for your hard work. This is my first Jenkins issue in two years of usage.

BTW, I attempted simple jar substitution with trunk of svnkit, and that did not work. Bunch of missing class def exception.

Why not allow usage of the command line client, instead of just SVNKit? At least this way, you're not always dependent on a particular downstream product?