[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Preventing "Dirty" Checkins

From: Greg A. Woods
Subject: Re: Preventing "Dirty" Checkins
Date: Wed, 29 Sep 2004 14:52:12 -0400 (EDT)

[ On , September 28, 2004 at 12:06:18 (-0700), Ones Self wrote: ]
> Subject: Preventing "Dirty" Checkins
> I'm running a CVS server which compiles and tests the current
> files in CVS every hour.  I would like to make new checkins
> available _only_ if they compile and pass the tests.

You don't want to use CVS then.

You need and want to use a tool called Aegis, or else something very
much like it.

I.e. you need to use a version tracking system that inherently supports
the concept of a two-phase commit.

Aegis acutally does the regression tests on every commit (or at least it
does this by default), as well as (optionally) implementing a manual
second "approval" commit (so in a sense Aegis is a three-phase system).

Furthermore new changes cannot be committed unless a new test is also
provided to make sure the changes are not broken ever again (unless they
are explicitly undone).

                                                Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <address@hidden>
Planix, Inc. <address@hidden>          Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]