search

jenkinsci / scm-sync-configuration-plugin

Jenkins scm-sync-configuration plugin
https://plugins.jenkins.io/scm-sync-configuration/
MIT License
115 stars 123 forks source link

Use Subversion Workspace Version from global config #12

Open SterlingPeet opened 11 years ago

SterlingPeet commented 11 years ago

I am having difficulty attempting to debug my scm-sync-configuration instance, and I have my global Subversion Workspace Version set to 1.6. The local machine has the svn 1.6 command line utility installed, but I cannot inspect the scm-sync working directory due to the following error :

speet3@hotwheels:/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration$ svn st
svn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy.  Please upgrade your Subversion client to use this
working copy.

scm-sync-configuration-plugin should use the global Subversion Workspace Version to set its working copy layout.

danielpetisme commented 11 years ago

The stack is cristal clear you need to use a SVN 1.7 compliant client. Personnally, I use SVNKit 1.7.9. It's a pure Java implementation of a Subversion client. You can use it as a library to embed in you code or a simply as a classical client. $SVNKIT_HOME/bin/jsvn help

The SCM-SYNC plugin relies on MAVEN-SCM-API library. And I'm affraid that is using the SVN 1.7 as standard.

It could be usefull to be able to select the version of the subversion client to use by the plugin or re-use the version define in th Jenkins subversion plugin.