This report has been sent

Apache Gump is a cross-project continuous integration server. It is different from "usual" CI servers in that it expects the individual project builds to succeed; its purpose is to check the integration of a project with the latest code rather than a fixed version of the project's dependencies. If you want a more traditional nightly build server, Gump is not for you. Use Gump if you want to know when a change in your dependencies breaks your project or when your changes break other projects.

Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate.

Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds many ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and log4net.


No development activity at all, no issues.


There are no Board level issues.


The Gump project really consists of two parts, the code base for the project and the ASF installations[1] running this code base to build many ASF projects as well as some related projects.

The code base mostly does what its current users need so there isn't much development going on at all. No new committers have been added.

All ASF committers have write access to the metadata that configure the ASF installations. There are a few people contributing across all projects and a few additional people maintaining the metadata of the projects they are interested in the most.

No changes to the PMC.

All in all the community is pretty small by now and it has been a long time since a new project has been added to the Gump runs because the project had asked for it - when we've added new projects over the past two years the driver has been the Gump community. It looks as if most projects are content with the existing vanilla CI options.




The ASF installations of Gump work on the latest code base almost all of the time. The project is in a state of a perpetual beta. There have been no releases.


The infra team has provided us with a VM to run Gump on top of Apache Harmony but it is currently not used, we'll hand it back to infra so it doesn't waste resources.

At one point in time a Gump run on the FreeBSD jail created many core dumps that filled up the disk space shared by all jails. Gump is now set up to not allow core dumps since nobody would want to look at them anyway.

Project Branding Requirements

We've updated the first sentence of the description to match the revised requirement. We believe to meet all requirements except for one: The logos still need a "TM" symbol, waiting for somebody with the skills required to make the change. Unfortunately the Gump community doesn't seem to include a single person with said skills.


As of Fri, 10 Jun 2011 the ASF installations check out a bit less than 180 source trees (115 from the ASF repository) and try to build a bit less than 800 "projects". A complete Gump run takes about seven and a half hours on vmgump or the FreeBSD jail about six and a half hours on the MacOS X server where more projects fail to build and thus less time is spent building dependent projects.

Some builds have been removed since the projects moved to the Attic (regexp, for example) or were unmaintained and always failed to build anyway.

[1] the main instance at , a FreeBSD jail at and a Mac OS X Server at

Drafts/BoardReports/20110615 (last edited 2011-06-13 05:38:47 by StefanBodewig)