Christopher Arndt wrote: > Steven Mohr schrieb: > >> my project has reached a state which is adequate to present it to you. I >> would say it's in a beta state. >> So first you can take a look at http://91.121.85.25:8010/waterfall. >> > > Looks impressive. Though I can hardly tell what all the information > means! ;) Looks like I finally have to fully read the buildbot > documentation! > > We should probably put this on a subdomain of turbogears.org, or at > least set up a redirect from the main turbogears web server. Is it > possible to run the webinterface behind an Apache/nginx reverse proxy? > > >> This >> is the status display of the >> build process. You see the tasks, their status (yellow = in progress, >> green= everything okay, red = failed) >> and link to a report of their stdio. >> > > For more information about the build, see also: > > http://91.121.85.25:8010/index.html > > >> But much more important I've to configure two things and the community >> has to tell me which way I should do this. >> >> First: How to notificate the commuinity about failed builds? >> The waterfall display is very uncomfortable and hard to read. You can't >> see which bot build the task, which python >> version and which OS. Buildbot has two other ways to send messages at >> the moment: per mail or per irc. >> I think the mail version is better. I talked with Chris about it and >> perhaps is a new google group (turbogears-build) >> the best solution. But perhaps you would like to have an irc channel >> with status reports too. >> > > IMHO definitely mail, but maybe Jabber would be a nice extra. But we're > open to suggestions. > They just support IRC at the moment but Jabber could be implemented in the future. They have an interface to add new status notifier but in the documentation they write that they have to add a better documentation of this feature. > >> Second: >> What event should start a build? >> Should they be started after a period of time, SVN activity or via a >> commandline call at server side. >> Every build task could have its own trigger. So what tasks do you need >> and what action should start them? >> > > Perhaps you could explain briefly what kind of builds we have so far? > We have one build for TG1, one for TG11 and TG2. These builds download source from SVN, install all dependencies, install TG, run the core tests, build all possible quickstart projects, test these projects and build an egg. Then we have builds for Cheetah and cElementTree. These builds download the source and build eggs. And builds for SimpleJSON, RuleDispatch and PyProtocol. These steps downloads the source from PyPi, run tests and build an egg. The build of the dependencies like SimpleJSON or Cheetah are created by an functions so it's easy to add more of them. > Chris > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
