People have been asking me at the Subversion Summit for more and better
information for failed builds, without needing to go to the buildbot web
page and search for the logs of the failed build.
Since then, some changes have been made to the buildbot configuration
(more specifically, the buildbot code) to answer these request (and other).
First, in the emails send to svn-breakage buildbot now adds the last 100
lines of the last step were the build failed. Failed builds due to
network problems or buildslave issues can be easily spotted this way.
Second, the buildbot has now both an RSS and ATOM feed for the FAILed
builds. The links to the feeds are in the topleft corner of the buildbot
webpage: http://www.mobsol.be/buildbot/ .
This is all new code, so if you have remarks of problems please let me
know and it will be fixed.
Third, Erik has changed the buildslave he's managing to start testing
ra_svn instead of ra_local.
Next on the buildbot TODO list:
- finish the documentation of the try feature
- find more people willing to host a buildbot slave (other platforms,
other development environments, more slaves sharing the load)
- setup a new build scheduler which allows us to cycle through all ra/fs
and build configurations
- start planning the move to another more reliable server
- integrate nightly builders (like Jani's) to get a more complete view
of all the tested configurations and platforms. This would also answer
David Glasser's request to have a view on the stability of each branch)
Lieven
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 8 00:01:35 2006