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

Re: SVN server and client incompatibility - quick question

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Mon, 3 Dec 2012 08:00:58 +0100

Guten Tag Z W,
am Sonntag, 2. Dezember 2012 um 20:52 schrieben Sie:

> 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.

This doesn't sound like the initial checkout was made by the
1.6-branch of Subversion, but would mean that Jenkins wouldn't be able
to update or do anything with the working copy at all. Check the
version of your Subversion plugin and if updates to the working copy
gets applied.

> Is the error message correct that Jenkins SVN client is a higher
> version that our SVN server ?

At least some client created a more current working copy than which is
needed by your commit which results in the error. The easiest way is
to upgrade your Subversion client in Jenkins and use proper 1.7
working copies if Jenkins is the only one who need to access those. Is
use some 1.7 working copies for some month now without any problems.

> Do we use a lower svn version or higher svn version in the Jenkins
> System configuration to fix this issue ?

The version of the clients an server don't matter, the problem is only
that you need to access the working copies with the same version and
it's preferable to let Jenkins be the only one doing whatever in his
working copies.

> 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 ?

As you working copy already seems to be in version 1.7 forma,t it
should be enough to update your plugin and configure Jenkins to use
1.7 format.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2012-12-03 08:01:28 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.