Re: the master build (was Re: martin fowler paper on continuous integration)

[Ken Wood <kw...@i2.com>]

We've had our build results on internal web pages for
almost 3 years. Very simple process:

  1. Build script re-directs all messages
     to a log file.

  2. Build script launches a separate program
     that 'watches' the log and every 15 seconds
     updates a web page that show's the build's
     status. That web page has on it links that
     show us the complete build log, or summary
     information. It also has links that execute
     CGI scripts to kill a running build, or
     start a build.

XML and servlets will also do the job, but servlets
didn't even exist when we started, so we use HTML
and CGI.

Diane Holt wrote:
> 
> --- mpfoemme@ThoughtWorks.com wrote:
> > Basically, our script runs a bunch of steps (checkout, build, run, test)
> > which each generate XML reports, and then at the end we merge them all
> > together to get a complete report. Then we have a servlet that serves up
> > this XML using stylesheets, plus displays a list of previous builds and
> > current build status. Ant can already generate an XML report
> 
> Being as new to XML as I am to Java, I'm not sure what all would be
> involved in doing something like this, but having nightly build and test
> results available on an internal web-page is something I'd be very
> interested in finding out how to do. Is anyone currently doing something
> like that, who'd be interested in sharing how they're doing it? Or, if
> anyone has just the (semi-specific) outline of what it would take, I'd be
> very interested in at least that much.
> 
> Thanks,
> Diane
> 
> =====
> (holtdl@yahoo.com)
> 
> __________________________________________________
> Do You Yahoo!?
> Send instant messages & get email alerts with Yahoo! Messenger.
> http://im.yahoo.com/