[Mono-devel-list] Automated builds

[Ben Maurer]

Well, `make bootstrap' is a target that should really always be
successful. If you have to clean your tree, the script is not doing its
job.

I fixed a few issues today, can you try it out again?

IMHO, there is value to both a `fresh' build and a `bootstrap' build.
The fresh build, one created from a fresh tree, would make sure that we
could build from scratch. The `make bootstrap' one would simulate the
process developers must go through. 

-- Ben

On Thu, 2004-05-13 at 14:59, Jaroslaw Kowalski wrote:
> Hi guys!
> 
> I really dream of a tinderbox-like automated build system that would detect
> non-buildable CVSes early. Today I've encountered 3 separate issues that
> prevented "make bootstrap" from running correctly.
> 
> With repeatability in mind I've developed a clean and repeatable mono
> rebuild script:
> 
> 0. Backup the entire mono tree (/opt/mono in my case)
> 1. cvsclean of "mcs" and "mono" modules - this gets rid of every
> file/directory not in CVS
> 2. cvs update
> 3. (cd mono && make bootstrap && make install)
> 4. (cd mcs && cvsclean . && make install) - to make sure the new setup is
> able to recompile itself when installed
> 
> In case of a failure I restore everything from a backup copy. On success I
> zip the entire mono setup as "last-known-good" configuration that I can
> return to.
> 
> This guarantees that I have a repeatable and dependable build. I usually run
> this as a cron job on my Fedora Core 1 machine that is 99% idle and can do
> this task easily.
> 
> If anyone is interested I can send you a notification + a build log on each
> failure and then again on each "fixed" build.
> 
> Jarek
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list