Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 746DC1164E for ; Thu, 3 Jul 2014 21:07:47 +0000 (UTC) Received: (qmail 17660 invoked by uid 500); 3 Jul 2014 21:07:46 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 17626 invoked by uid 500); 3 Jul 2014 21:07:46 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 17614 invoked by uid 99); 3 Jul 2014 21:07:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 21:07:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of markphip@gmail.com designates 209.85.216.177 as permitted sender) Received: from [209.85.216.177] (HELO mail-qc0-f177.google.com) (209.85.216.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 21:07:41 +0000 Received: by mail-qc0-f177.google.com with SMTP id r5so760264qcx.22 for ; Thu, 03 Jul 2014 14:07:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=uSAeM3s7t/70/KjOMzMZw0IljCMrDbuLbAtjXB+jSwQ=; b=TG0t8dYFUycV14loMu1D/3KnLNqiJGZLhrIc8VGEZ5Top4tQ4s2D79Gd3LpJ0e6A/J 3zypQIzaTq4f4OYSWxX/UIqvaUgrjgk72R/SAtCEJyOe5EzzRqZ7nYCodEqIV2gLlTbq QmdR11Zul2sioXbcEPsSboV9ywuVzXB4Wt8AgO3Nuloakdxe0F/casB/o7D5Bni1idcb +ShoJe/Em065euQpbqekMXAweDIXlaL7DbjwlqMKXGTgHJ8TTc33i7S2TzgJzwPfCEpN hPqq7SHPnzV6nwt9uzUaLxYprhc/gDt+Iu2n6tSwDxsbKMAsDTz9zXlL+iKuD0rLfqpG IOUA== X-Received: by 10.140.101.115 with SMTP id t106mr10834245qge.91.1404421640404; Thu, 03 Jul 2014 14:07:20 -0700 (PDT) Received: from [10.0.1.113] ([199.204.196.170]) by mx.google.com with ESMTPSA id d4sm304803qag.5.2014.07.03.14.07.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Jul 2014 14:07:19 -0700 (PDT) References: <043e01cf95e0$bd56f7c0$3804e740$@qqmail.nl> <53B525AD.903@wandisco.com> <20140703154731.GB2400@larry.stsp.name> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <017E2FBE-59ED-48D3-BAE6-122BADE5C8E7@gmail.com> Cc: =?utf-8?Q?Branko_=C4=8Cibej?= , "users@subversion.apache.org" X-Mailer: iPhone Mail (11D201) From: Mark Phippard Subject: Re: Extend E155021 message to include supported format version Date: Thu, 3 Jul 2014 17:07:17 -0400 To: Notes Jonny X-Virus-Checked: Checked by ClamAV on apache.org > On Jul 3, 2014, at 3:01 PM, Notes Jonny wrote: >=20 > Hi Mark >=20 >> On Thu, Jul 3, 2014 at 5:50 PM, Mark Phippard wrote:= >>> On Thu, Jul 3, 2014 at 12:43 PM, Notes Jonny wrote: >>>=20 >>> Hi Stefan >>>=20 >>>=20 >>>> On Thu, Jul 3, 2014 at 4:47 PM, Stefan Sperling wrote: >>>>> On Thu, Jul 03, 2014 at 10:58:35AM +0100, Notes Jonny wrote: >>>>> I guess the other idea is to promise to only allow ".svn format" >>>>> updates every 5 years? I can't think that I've noticed any >>>>> improvements since I've been using new formats.. >>>>=20 >>>> The 1.8 format added support for local move tracking, for instance. >>>> http://subversion.apache.org/docs/release-notes/1.8.html#moves >>>=20 >>>=20 >>> Many thanks for your reply. >>>=20 >>> I'm still suffering the version collisions. I was going to join >>> tortoise svn users list, but I thought as I am already discussing here >>> I will ask you. >>>=20 >>>=20 >>> I've installed TortoiseSVN 1.7.7 (which uses svn 1.7.5) and it can't >>> access the checkout from Jenkins (which is supposed to be "1.7" >>> format). Actually Tortoise is offering to upgrade to "1.7". I am a bit >>> surprised as it is already a 1.7x release. >>=20 >>=20 >> Note that Jenkins uses SVNKit, not the Subversion libraries and it has a >> global preference that indicates which working copy format it will create= . >> I believe it defaults to 1.4, but it can be changed to 1.7 if you are on a= n >> updated version of the plugin. >=20 > Interesting. I have set it as 1.7 in the "Manage Jenkins", which means > it works with 1.7.5 cygwin svn client. But not 1.7.7 TortoiseSVN.. That can't be true. All 1.7 clients use identical formats.=20 >=20 >=20 >>> I'm a bit confused why TortoiseSVN can't handle. I will probably go >>> back as a binary search to find a TortoiseSVN that works.. this is >>> such a high cost on users (already a large amount of money/development >>> time used up. I'd happy donate an amount of money to get a fixed .svn >>> standard format for the next decade..) >>=20 >>=20 >> Why do you need to access the working copies of your continuous integrati= on >> server with TortoiseSVN? >=20 > On Jenkins machine it has some steps: >=20 > A) Jenkins SVN checkout > B) Jenkins Triggers build > C) Jenkins Triggers automated testing of the build. > D) Build checks in the results to SVN Can't Jenkins do D? Mark=