[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SVN server and client incompatibility - quick question

From: Z W <mpc8250_at_gmail.com>
Date: Sun, 2 Dec 2012 14:16:58 -0800

Hi

We are new to SVN.

We found that our Jenkins CI 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 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.
Received on 2012-12-02 23:17:32 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.