tracking multiple "test" groups

["Coleman, Brandon" <Br...@goHastings.com>]

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.
 
Brandon
 

RE: tracking multiple "test" groups

[Bob Archer <Bo...@amsi.com>]

From: Coleman, Brandon [mailto:Brandon.Coleman@goHastings.com]
Sent: Tuesday, December 07, 2010 2:38 PM
To: users@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.

Brandon