SVN server and client incompatibility - quick question
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 *
Re: SVN server and client incompatibility - quick question
On Dec 2, 2012, at 16:16, Z W wrote: > 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 > > > > 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 ? The version of the Subversion server does not matter. It only matters that you access your working copy only with Subversion 1.6 clients, or only with Subversion 1.7 clients, and not a mixture of the two as you are evidently doing.
SVN server and client incompatibility - quick question
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
Size of wc.db
Hi, [Please cc] I have a query regarding the size of wc.db. I checked out the webkit svn repository (which is rather large). I then excluded most of it with: svn update --set-depth=exclude LayoutTests The resulting .svn dir is about 19000 files and 522MiB. However, wc.db is 203MiB. This seems huge compared with the size of the checkout. Is this normal? Is there any way to get this file to be smaller? Regards Ross Lagerwall
1.7.7 svn client x64 crashes while committing with credentials provided on the command line.
Hi guys, not sure whether it was already reported or not, but just in case it's not yet. I've got consistent crash of the 1.7.7 svn client x64 (tried both from Collabnet and Slik). The crash only happens when the credentials are required and when they were provided on the command line. Something like: svn ci MY_WORK_DIR -m "comment" --username USER --password PASSWORD Does not happen with 1.7.6. cheers, Mikhail Pereiaslavski _ This email is intended only for the use of the individual or entity named above and may contain information that is confidential and/or privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this Email in error, please notify us immediately by return email or telephone +61 2 9966 1066 and destroy the original message. Thank You ___
RE: 1.7.7 svn client x64 crashes while committing with credentials provided on the command line.
Sorry, forgotten to attach the crash log. The crash happens both on XP x64 and Windows 7. <> _ From: Mikhail Pereiaslavski Sent: Monday, 3 December 2012 5:25 PM To: 'users@subversion.apache.org' Subject: 1.7.7 svn client x64 crashes while committing with credentials provided on the command line. Hi guys, not sure whether it was already reported or not, but just in case it's not yet. I've got consistent crash of the 1.7.7 svn client x64 (tried both from Collabnet and Slik). The crash only happens when the credentials are required and when they were provided on the command line. Something like: svn ci MY_WORK_DIR -m "comment" --username USER --password PASSWORD Does not happen with 1.7.6. cheers, Mikhail Pereiaslavski _ This email is intended only for the use of the individual or entity named above and may contain information that is confidential and/or privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this Email in error, please notify us immediately by return email or telephone +61 2 9966 1066 and destroy the original message. Thank You ___ svn-crash-log20121203165349.log Description: svn-crash-log20121203165349.log
Re: 1.7.7 svn client x64 crashes while committing with credentials provided on the command line.
Guten Tag Mikhail Pereiaslavski, am Montag, 3. Dezember 2012 um 07:25 schrieben Sie: > not sure whether it was already reported or not, but just in case it's not > yet. It's a known issue: http://mail-archives.apache.org/mod_mbox/subversion-users/201211.mbox/%3c20121104101302.gd27...@ted.stsp.name%3E Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@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
Re: SVN server and client incompatibility - quick question
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.schoen...@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
