-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of tanager Sent: 15 February 2012 19:41 To: [email protected] Subject: Re: will latest 1.7 schedule hold?
Henk van Voorthuijsen wrote: > > > > David Carson-2 wrote: >> >> I'm waiting on deploying an SVN server that will use svn 1.7 until >> SvnKit has released its own full 1.7 support. This is because we use >> several tools that themselves use SvnKit and these tools do not >> properly handle the changes in 1.7. >> > > We have successfully upgraded our repository to 1.7. As long as you > keep your clients exclusively to 1.6, there should be no problem. > > But yes, a bit more current information on the download page would be > appreciated. > > Henk van Voorthuijsen > There are reasons why this still might not be sufficient. We use Jenkins and the Subversion plugin for Jenkins uses SVNKit. Even though the latest Jenkins svn plugin was released yesterday, the Changelog is quiet on whether or not the 1.3.7 version of SVNKit was integrated (so I assume it was not). That means, Jenkins+svn still does not work with a 1.7 svn server, if "svn:" protocol is required (as it is for me). Unless I'm missing something, I don't think that's correct. The Jenkins Subversion plugin clearly includes older versions of SVNKit internally and is capable of using any of 1.4.x, 1.5.x and 1.6.x Subversion client formats for its checkouts. It's a system wide configuration option in Jenkins->Manage Jenkins->configure system->Subversion->Subversion Workspace Version. All our workspaces are on version 1.4 even though our server is version 1.5.6, simply because that was the default when this feature first became available, and it's never caused us problems. Before this feature was available, we used 1.4 clients, including SVNKit against a 1.5.6 server without any issues over the 'svn:' protocol. Even better, Jenkins doesn't care if you bump the format of a workspace to a newer version by running a newer client, so long as it is a supported version. It silently and transparent switches the plugin to use the compatible format on running that build. So if 1.7.x isn't a choice when configuring the system, just don't try to use a 1.7 client in the slave workspace. Tony. My guess is that the Jenkins svn plugin will not bother to integrate a new SVNKit until 1.7 is available. Thanks, David -- View this message in context: http://old.nabble.com/will-latest-1.7-schedule-hold--tp33296760p33331342.html Sent from the SVNKit - Users mailing list archive at Nabble.com. ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2112/4811 - Release Date: 02/15/12 ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________
