I have the (very very) basic autobuilder up and running. Currently it
is doing a build every night on a couple of machines - a Linux box of
mine and nagoya. Builds can either be against "known-good" versions of dependencies (e.g Xerces 2.3) or current cvs.
Currently I am only building the xml-security library, which relies on both Xerces-C and Xalan-C. The only tests that are run (other than trying to build) are for the security library (which is currently failing due to a bug in Xerces).
You can see the output of the runs at
http://nagoya.apache.org/~blautenb/autobuild/logs/
*Very* ugly at the moment, but I haven't gone for pretty yet. (I'll clean that up as I go along.)
The autobuild-report-nagoya-date files are an overall report on all the things it tried to build and where they failed. The autobuild-security-... and autobuild-security-noxalan-.... are the particular systems/tests it tried to do.
I'd like to add a specific build for Xalan, but I need to have a set of tests that exercise the library well enough to judge the success of the build.
There are the files in xml-xalan/c/Tests, but I'm not sure if these are the most appropriate, so all thoughts very welcome.
Finally - are people comfortable if I send error outputs to xalan-dev? The idea is that the list should only ever get an output when a build fails, but if something goes wrong in a file in CVS and a number of builds happen on one night (e.g. FreeBSD, Solaris x 2, NetBSD, Linux) then we could be hit with a barage of mails. Mind you, my aim would be to stagger the builds on the various systems so that we'd minimise what we got on any given night.
I'm going to similarly go to the Xerces-C group once we have things running smoothly for Xalan-C to see if they are interested.
Cheers,
Berin