On 3/27/06, Julien Gilli <[EMAIL PROTECTED]> wrote: > Hello, > > > On 3/27/06, Luis Villa <[EMAIL PROTECTED]> wrote: > > When I looked at buildbot last year it seemed like setting it up to > > build multiple, consecutive, interdependent tarballs (i.e., gnome) > > > > Could you please give us further details about what was the technical > problem by the time you tried?
Any GNOME tinderbox must take at minimum an ordered list of CVS roots, ideally drawn from jhbuild (since that is basically the canonical list of modules), and be able to build that list.I could find no support for a *list* of roots in buildbot, just a one-at-a-time type support. [It did seem like I could code it up myself, but it seemed non-trivial, and I had other things to do.] That is at a minimum. Ideally it should also be able to: * understand dependencies in that list, so that if a build of glib fails, the entire run restarts, but if a build of gok (or something else which nothing depends on) fails, the run continues after gok. * distinguish between build and test failures. If *building* gtk fails, the failure needs to be reported and the entire build run must restart. If an obscure a11y test of gtk fails, the failure must be reported and the build *must continue*, otherwise there would never be a successful build. I had to hack this last 'feature' into jhbuild when I was using jhbuild, but IIRC it was the only major change I had to make to jhbuild, which made it much more appealing to me than buildbot. That said, buildbot has a lot of other magical, cool features, so I agree strongly that if someone had the time to hack these features into buildbot, using it would be ideal. Luis _______________________________________________ gnome-love mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-love
