[wpkg-users] Tips for testing new/upgraded packages before general deployment

[Dave Ewart]

On Tuesday, 05.04.2011 at 12:26 +0200, Natxo Asenjo wrote:

> > [...]
> >
> > The issue I have, however, is if I want to test the *upgrade* for an
> > existing, already deployed app.  Let's say, in the above example, I
> > have an upgrade for 'app2'.  I want to be sure that the upgrade
> > works, using my 'testing' VM, before I make it available to the
> > 'typical' group.
> >
> > How do people do that, generally?  My main constraint is that there
> > must be no circumstances under which the 'typical' group can pick up
> > on the upgrade until I've fully tested it.  The 'typical' group
> > should stay with the non-upgraded 'app2' (or only install the older,
> > non-upraded version of 'app2' if they've not seen it before).
> 
> what we do is have serveral (mercurial) repositories: testing,
> staging, production (for instance).
> 
> The testing vm's get their configs from \\host\share\wpkg-testing, the
> staging machines from \\host\share\wpkg-testing and the production
> from \\host\share\wpkg-production.
> 
> [...]

Ah, I understand the general approach.  I hadn't considered the
possibility of using multiple repositories in this way.  Sounds like a
good idea.

Many thanks...

Dave.

-- 
Dave Ewart
davee at ceu.ox.ac.uk
Computing Manager, Cancer Epidemiology Unit
University of Oxford / Cancer Research UK
N 51.7516, W 1.2152