Andy Armstrong wrote: > On 3 Jan 2008, at 09:15, Adrian Howard wrote: >> There's also Michael's rather swizzy Smolder project. >> >> http://sourceforge.net/projects/smolder > > > Indeed. Smolder++. You still need something to manage a build farm > though. I got about 80% done on Test::SmokeStack (leaving only another > few 80%s to do). That was going to talk to Smolder.
Thanks for endorsement :) > Turns out that buildbot is almost exactly what SmokeStack was going to > be - so I'll probably divert my attention to buildbot and get that > talking to Smolder instead. Actually I've been thinking the same thing! Buildbot just needs to send a TAP Archive to a smolder install. That way buildbot can concentrate on making it easy to do builds and runs on multiple platforms/machines. And Smolder can concentrate on making useful reports. > My Python Fu is weak but I spent a productive couple of hours hacking > about with buildbot last night. My aim is to make it easy to test all > the modules in my SVN against multiple Perl's on multiple machines and > have the config changes to add a new module be as minimal as possible. Shouldn't be too much python required. Just tell prove to --archive and then find some HTTP library to send it to smolder. Or you could just fork off and use the smolder_smoke_signal script that comes with smolder to do the actual work. In fact that's probably the best way since that's the supported interface right now for sending reports to smolder in an automated way. -- Michael Peters Developer Plus Three, LP
