[Top][All Lists]

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

Re: Preventing "Dirty" Checkins

From: Robin Rosenberg
Subject: Re: Preventing "Dirty" Checkins
Date: Fri, 01 Oct 2004 20:38:08 GMT
User-agent: KNode/0.8.0

Pierre Asselin wrote:
> Hm, my language was ambiguous.  What the loginfo would trigger is
> one script, running on the test machine, that updates the test sandbox,
> builds, runs the tests, and finally moves the tag if the tests pass.

Trigging rebuilds for every commit is insane. 

I run a job for one project every 15 minutes that checks if there are any
checkins since the previous build using cvs histor and also checks that non
checkins happened during the last ten minutes. The ten minute check is
there to lessen the risk that a build starts in the middle of a check-in,
giving false negative status reports).

Then the build process starts, tagging everything in the project with a
unique tag, exporting from CVS using that tag and then it building the
project. The compilation errors and a summary are sent via e-mail to all
interested parties and an internal web is updates with a pass/fail flags
and a link to the build directory for reference and retrieval of the

It does waste disk space, but that's cheap. It is also easy to prune old

-- robin

reply via email to

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