Tony Sweeney-3 wrote:
>
>
> 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.
>
>
There was a bug in SVNKit, fixed in 1.3.7, which made use of SVNKit + "svn:"
protocol impossible with a 1.7 svn server. It makes no difference what kind
of client-side wc format you want.
Anyway, I now see that Friday we will see a beta with all functionality.
This is truly great news!
--
View this message in context:
http://old.nabble.com/will-latest-1.7-schedule-hold--tp33296760p33331771.html
Sent from the SVNKit - Users mailing list archive at Nabble.com.
