[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[RFC] Move buildbot master to ASF infrastructure

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: Sun, 15 Nov 2009 15:06:16 +0100

Hi all,

while we're migrating mailing lists and the svn repo to the ASF
infrastructure, let's discuss what we want to do with the buildbot.

The ASF provides 4 different build services (see
http://ci.apache.org/) and Buildbot (the one we use) is one of them.

Based on a long chat with Gavin McDonald from ASF infra on IRC last
week, I propose to integrate our Buildbot master into the ASF's. This
has some (obvious) benefits:
- although our buildbot master has been stable since we migrated it to
Justin's Mac, I assume the ASF infrastructure team can do a better job
of hosting and maintaining such setup in a secure environment.
- ASF's buildbot already has Ubuntu and Windows server 2008 slaves
(and according to Gavin also Windows XP 64 bit and Solaris) and there
are plans to add more. There's no Mac yet, but we have one in our
- it has more features (http://ci.apache.org/buildbot.html), and -
more importantly - the maintainers are open (and have time) to improve
the setup based on our requests.

Sticking with buildbot allows us to keep the existing buildbot slaves,
if the owners choose to do so. Also, out of the 4 available options it
seems best fitted to our use case (C code, custom test scripts and
builds on multiple platforms).

There are some things that aren't really clear yet:
- the ASF buildbot is shared for 20+ projects. I know slaves can be
reserved for certain projects, but what's the impact of building
projectA first, and then build subversion on the same slave.
- do we use slave's system libraries, or do we need to build a
specific set of versions of libraries used only for the subversion
- the waterfall view is shared between all projects and buiders
(http://ci.apache.org/waterfall). Is that okay for us? Or should we
work on a Subversion specific view.
- if there are project + slave specific build problems, what are our
options to get the needed logs/info and fix the issues?

We'll get more clarity on these points when working on the migration
with ASF infra.

If you guys are ok with this I'll create a ticket in the ASF Jira and
work with them to integrate our master. Given my busy schedule I'll
probably need some help setting up new buildbot slaves.

So, thoughts? Remarks?


Received on 2009-11-15 15:06:50 CET

This is an archived mail posted to the Subversion Dev mailing list.