[Openmcl-devel] First draft!

[Barry Perryman]

but instead of being built twice we get 24 builds a day, for possibly no 
changes :)

What about combining the two approaches and use a method similar to the 
continuous integration software tools*.  If we know that the site has been 
updated since we last rebuilt it, BUT there have been no changes in the last 
say 10 minutes then we rebuild the site. That way, multiple checkins are not 
going to build the site multiple times and we also aren't going to be 
rebuilding the site when no mods have been made.

Depending on the scheduling of the rebuild you'll only wait a maximum of:
    (+ cron-task rebuild-time inactivity-time)
before the changes are available.

Barry

---
* Software such as Cruise Control.NET for example.
[Hello, My name's Barry and I'm a .NET developer]

>From: Dan Knapp <dankna at accela.net>
>To: openmcl-devel at clozure.com
>Subject: Re: [Openmcl-devel] First draft!
>Date: Tue, 6 Jul 2004 22:10:42 -0400
>
>   I've got a reason not to do that. :)
>
>   If one were committing, say, changes to two different stylesheets, that 
>would be
>two commits and every file would get rebuilt twice.  The one-hour delay 
>serves
>the purpose of allowing several changes to be made together, or soon after 
>each
>other, with the knowledge that they will all be applied at once.
>
>-- Dan Knapp
>
>_______________________________________________
>Openmcl-devel mailing list
>Openmcl-devel at clozure.com
>http://clozure.com/mailman/listinfo/openmcl-devel