As can be clearly seen by the huge number of jira bug reports, forum questions, and plug-in wiki comments, the subversion plug-in is a failed implementation.

The reason for this is quite simply that it is not possible to rely upon svnkit (TMate software) to maintain timely compatibility with subversion (Apache). Incompatibilities across default Jenkins svnkit version and host machine version cause confusion and error. Availability of additional plug-in (not default bundled version) is equally confusing.

Proposed solution is to allow Jenkins to to use the host (master and slave) machine subversion client.