[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Cruisecontrol/SVN upgrade plan

From: emerson cargnin <echofloripa.yell_at_gmail.com>
Date: 2007-05-29 12:46:28 CEST

Hi all

We are doing an upgrade on our continuous integration machines and I
would like to ask you a couple of questions...

- Is an anti-pattern having CC and SVN server running in the same machine?

We are a group of +- 40 developers using subversion and I suppose that
svn doesn't take that much of the machine (which will )

As we will have 2 dedicated machines for SVN/CC i though in opting to
use them in a fail over approach instead of separating the services.
What's the best practice on this matter?

- Is the CC 2.6.2 straightforward to upgrade from 2.5?? In 2.5 I had
to change a lot of xslt and css to solve the memory problem, I assume
this was corrected already on 2.6.2. is this version stable enough?

Which is the best mechanism to synch the SCN servers??

How to have a fail-over in CC to avoid send emails twice when both
machines are running?

Thanks guys

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 29 12:48:19 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.