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

RE: tracking multiple "test" groups

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Tue, 7 Dec 2010 14:57:13 -0500

From: Coleman, Brandon [mailto:Brandon.Coleman_at_goHastings.com]
Sent: Tuesday, December 07, 2010 2:38 PM
To: users_at_subversion.apache.org
Subject: tracking multiple "test" groups

I currently use SVN with Feature branches that are tested, merged to trunk, compiled and then sent to a small group of test production machines. If the code at the test machines works as planned for a test period then the compiled code is deployed to all production machines, and if a bug is found, the branch is removed from trunk and the binaries changed back to the old state. We would like to have two (possibly more) groups of test production machines with different sets of test code at each test group.

What is the suggested way of keeping two sets of test code? My thought was to compile the branches I would like to go to a test group in their branch directory and just keep them updated and compiled with the latest branches committed to trunk, but I want to know from others experience if there is a better way.

Received on 2010-12-07 20:57:54 CET

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.