title: Configure Subversion plugin in Jenkins to use 1.6 working copy
body: <p>I use the Jenkins Subversion plugin to checkout a working copy in Jenkins. A separate SVN client is used to extract some information from this working copy (which branch was used, which revision, etc.).</p>
  
  <p>The Subversion plugin creates a 1.7 working copy, which the other client can't handle (it is 1.6). <strong>Is there a way to configure the Subversion plugin to checkout a 1.6 working copy?</strong></p>
  
  <p>This question lists a way to configure the Subversion plugin: <a href="https://stackoverflow.com/questions/3417869/hudson-doesnt-checkout-using-symlinks-when-using-svn-subversion">Hudson doesn&#39;t checkout using symlinks when using SVN (Subversion)</a>
  So I started looking for all configuration options, and ended up on this page: <a href="http://svnkit.com/kb/user-guide-config-settings.html" rel="nofollow noreferrer">http://svnkit.com/kb/user-guide-config-settings.html</a> , but it is really incomplete.</p>
  
  <p>Also I found this: <a href="http://wiki.svnkit.com/SVNKit_FAQ#Q:_Can_the_current_SVNKit_version_be_forced_to_create_pre-1.5_format_working_copies.3F" rel="nofollow noreferrer">http://wiki.svnkit.com/SVNKit_FAQ#Q:_Can_the_current_SVNKit_version_be_forced_to_create_pre-1.5_format_working_copies.3F</a> , except that that property is ignored for new directories.</p>
  
  <p>I cannot use Jenkins variables to extract the branch and revision information, because the same script must also be able to run outside Jenkins. Updating the separate client is also not possible, because we are working with 'frozen' software on build systems. If all else fails I could downgrade Jenkins, but that's not preferred.</p>