Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of brane@wandisco.com designates
 74.125.82.182 as permitted sender)
Message-ID: <53B5B57C.5020300@wandisco.com>
Date: Thu, 03 Jul 2014 21:56:44 +0200
From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@wandisco.com>
Organization: WANdisco
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "users@subversion.apache.org" <users@subversion.apache.org>
Subject: Re: Extend E155021 message to include supported format version
References: 
 <CACZYS+q1V5G8XRP6NtCvH1u9QBnffR5ze1TDjt3DfD2ohJ5+Bw@mail.gmail.com>
	<043e01cf95e0$bd56f7c0$3804e740$@qqmail.nl>
	<CACZYS+q8Y_3BuBfCBA0ToYV86Pjj=vUr7e5v3Y5HJUkxON62Qg@mail.gmail.com>
	<CACZYS+p-8rXdD+dijmst_d1YnZZ7UVmE7R8jtzrQ-0-+fXZ46A@mail.gmail.com>
	<53B525AD.903@wandisco.com>
	<CACZYS+peD6Sj4v1_50+mDcgh8tBri7J2VsPcsV8TXJ71nSXxJQ@mail.gmail.com>
	<20140703154731.GB2400@larry.stsp.name>
	<CACZYS+qMOH97e7fHahC4NnRJhpwphf617vDaP+2s=y0agdVUpA@mail.gmail.com>
	<CAHFaGCpaV7+irSBwDck34eq9EVewFY0K+wLQ_xfX_e8k5sCzNw@mail.gmail.com>
 <CACZYS+qwUHjLwqf5HTcwaq61fCgpEgSU+hk3sGksP=6rUCWcCg@mail.gmail.com>
In-Reply-To: 
 <CACZYS+qwUHjLwqf5HTcwaq61fCgpEgSU+hk3sGksP=6rUCWcCg@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------000508020901030209070401"

This is a multi-part message in MIME format.
--------------000508020901030209070401
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 03.07.2014 21:01, Notes Jonny wrote:
> Why do you need to access the working copies of your continuous integration
> server with TortoiseSVN?
> On Jenkins machine it has some steps:
>
> A) Jenkins SVN checkout
> B) Jenkins Triggers build
> C) Jenkins Triggers automated testing of the build.
> D) Build checks in the results to SVN
> E) Developer fixes code, and commits files using TortoiseSVN.
>
> (D) is compulsory. (E) is Nice to have..

I'm not going to comment on (D), but you absolutely do not want to do
(E) in the sandbox used by your automatic build setup.

-- Brane


-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com

--------------000508020901030209070401
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 03.07.2014 21:01, Notes Jonny wrote:<br>
    </div>
    <blockquote
cite="mid:CACZYS+qwUHjLwqf5HTcwaq61fCgpEgSU+hk3sGksP=6rUCWcCg@mail.gmail.com"
      type="cite">
      <pre wrap="">Why do you need to access the working copies of your continuous integration
server with TortoiseSVN?
</pre>
      <pre wrap="">
On Jenkins machine it has some steps:

A) Jenkins SVN checkout
B) Jenkins Triggers build
C) Jenkins Triggers automated testing of the build.
D) Build checks in the results to SVN
E) Developer fixes code, and commits files using TortoiseSVN.

(D) is compulsory. (E) is Nice to have..</pre>
    </blockquote>
    <br>
    I'm not going to comment on (D), but you absolutely do not want to
    do (E) in the sandbox used by your automatic build setup.<br>
    <br>
    -- Brane<br>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <span style="font-face:sans-serif;font-size:9pt;line-height:18pt">Branko
        Čibej <span style="color: #f90">|</span> <span
          style="font-weight:bold">Director of Subversion</span>
        <br>
        WANdisco <span style="color: #f90">//</span> <span
          style="font-style:oblique">Non-Stop Data</span>
        <br>
        <span style="color: #ccc">e.</span> <a class="moz-txt-link-abbreviated" href="mailto:brane@wandisco.com">brane@wandisco.com</a></span></div>
  </body>
</html>

--------------000508020901030209070401--