Gnaaaah. Apart from the shiny UI this thing is unusable for this purpose. It runs a long-running ruby process for each project that it monitors. That would be around 150-200 in our case.
My server died two times today when monitoring about 30 processes. That's not gonna work. ;) I'll try figuring out whether buildbot can fit into this picture a little bit better. Christian Am Freitag, den 04.05.2007, 19:16 +0200 schrieb Christian Theune: > Hi, > > I've been trying to find a solution to run the individual tests of all > top-level projects in the repository. > > I've set up a cruise control server in our office that > monitors the SVN and automatically picks up any top-level project that > defines a buildout.cfg in its trunk. > > You can watch it work here: http://uter.gocept.com:3333/ > > It reacts to changes in SVN automatically. > > New projects will be picked up every 3 hours. > > This thing is experimental. > > Christian > > _______________________________________________ > Zope3-dev mailing list > Zope3email@example.com > Unsub: http://mail.zope.org/mailman/options/zope3-dev/ct%40gocept.com > -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Zope3-dev mailing list Zope3firstname.lastname@example.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com