Jenkins SVN client and svn server - quick questions

[zw]

Hi

We found that our Jenkins is configured to use Subversion Workspace Version 1.6 (svn:externals to file)
We also found that the SVN server is using SVN version Subversion 1.6.16
When running our build, we get the following errors:

Svn : Sending changes from your working copy to the repository :
ci --force-log -m A123 - Updating version.properties for x.x.x Build 3 - reviewed
--non-interactive /path/to/slave/workspace/hudson_Build/src/abc/version.xml
svn: The path '/path/to/slave/workspace/hudson_Build/src/abc/' appears to be part of a Subversion 1.7 or greater
working copy rooted at '/path/to/slave/workspace/hudson_Build'.
Please upgrade your Subversion client to use this working copy.

In our build.xml file used by Jenkins, we have
<svn>
           <commit file="${a.version.xml}" message="A123 - Updating version.properties for ${dex.version} Build ${build.number} - reviewed" />
</svn

Is the error message correct that Jenkins SVN client is a higher version that our SVN server ?
Do we use a lower svn version or higher svn version in the Jenkins System configuration to fix this issue ?

Would selecting lower svn version or higher svn version in the Jenkins System configuration affects the current job workspaces, ie deleting our job workspaces based on current svn client version 1.6?
Would the workspace be corrupted midway if we change the svn client version in the Jenkins System configuration to fix this issue ?
How do we fix this issue ?

Thanks for your help in your answers.

[Jeff]

I only see those errors if I check out a project with a subversion client that is based on 1.7 and attempt to use a 1.6 client with that project at a later time.  In my case, it had nothing to do with the server version.

For example, I use DropBox for my dev workspaces so that my work files are sync'd to home or other computers.  If I check out the files using a 1.7 client at work and I haven't updated SVN at home and am still using 1.6, I am unable to work with it at home and see similar errors.

My guess is that somehow there may be two different versions of SVN clients installed and somehow when it was checked out 1.7 was used, but Jenkins is also using 1.6.  But, I have no idea how that would be the case if it is only happening within Jenkins.

Make sure only one version of SVN is installed on the Jenkins server.  If you only have a 1.7 client maybe there is a compatibility flag that needs to be used.

--

Jeff Vincent
preda...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

I ♥ DropBox !!