last week, Gavin McDonald from the ASF infrastructure team integrated
the configuration of our buildbot master in the ASF buildbot master.
From now on the operational support of the *master* will be handled by
the infrastructure team (builds at apache.org).
The new master can be found at: http://ci.apache.org/buildbot.html.
You'll see on the waterfall page that the ASF buildbot has a lot of
slaves, used by svn and the other ASF projects. For people only
interested in the svn build status, Bert has prepared a page which
filters out all non-svn slaves.
You can find this page at:
The slaves - dedicated to the svn project - are still those maintained
by us devs. We don't use any of the ASF build machines yet (at least
not on buildbot, the hudson setup has a Solaris slave). We now have:
- a Windows 2003 64 bits VM, testing both ra_local and ra_serf and the
bindings (sponsored by SlikSVN, maintained by Bert)
- a Ubuntu 64 bits server, testing ra_local & the bindings (sponsored
& maintained by Hyrum)
- a CentOS 64 bits server, testing ra_neon & the bindings (sponsored
by WANDisco, maintained by Hyrum)
- a Debian 64 bits server, testing ra_svn (sponsored & maintained by Erik)
- a MacOSX 10.5 server, testing ra_neon & ra_serf (sponsored &
maintained by myself)
Some things have changed compared to previous setup:
- emails are now sent only on status change (from successful to
failed, from failed back to successful).
- those emails are sent to notifications at subversion.apache.org
- builds can not be started from the webpage (from now), but ...
- there's a bot in the #svn-dev IRC channel (subversion-bot) that will
notify the channel of failed/successful builds, and accepts commands
like starting & stopping builds.
I'll update the text and links in our development documentation shortly.
Thanks to Justin for supplying the old master server and Gavin for
doing the hard work migrating.
Received on 2010-05-31 00:05:16 CEST