Hi David, if non of the core Parrot developers answer you then let me, the newcomer do so.
Recently I have been involved in a little research where I was looking at various automatic build and test smoking systems. Among others I looked at the PostgreSQL build farm as well. See my blog entries: http://www.szabgab.com/blog/2007/07/1183825266.html I liked it very much though I have some issues that I think should be improved there too. Regarding Parrot, I think there was some discussion of moving it to use TAP::Harness and to use Smolder to collect the TAP based results. I am quite in favor of having something like the PostgreSQL build farm integrated with TAP::Parser and possibly Smolder and adding some other features as well. So I'd be glad to participate in your project and help making sure that the all the needs of the Parrot team are addressed. Gabor On 8/30/07, David Fetter <[EMAIL PROTECTED]> wrote: > Folks, > > I'm working on generalizing PostgreSQL's buildfarm code > <http://www.pgbuildfarm.org/>, an automated build and test system, and > of course I thought of Parrot. > > The requirements are very light: > > * Disk space for the source code and build > * Connectivity to the internet via HTTP or HTTPS > * Some way (cron, e.g.) to run jobs regularly > * Some way to get regular updates to one or more branches of the > source code > > Would people here be interested in running clients on various > architectures, OSs, compilers, etc.? What kinds of things would you > like to see in a status overview page like this one: > <http://www.pgbuildfarm.org/cgi-bin/show_status.pl> How about in > detailed build reports? > > Cheers, > David. > -- > David Fetter <[EMAIL PROTECTED]> http://fetter.org/ > phone: +1 415 235 3778 AIM: dfetter666 > Skype: davidfetter > > Remember to vote! > Consider donating to PostgreSQL: http://www.postgresql.org/about/donate > -- Gabor Szabo http://www.szabgab.com/
