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.


Low development activity to adapt to a difference between mvn 2.x and 3.x, the Mac OS X machine went live, 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.

Support requests for the non-public Gump installation running on top of OpenJDK7 dribble in and get addressed.


Only minor changes that lead to separate "install" builders for mvn2 and mvn3.


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 Mac OS X instance called Adam is now running the full set of projects.

The infra team has provided us with a VM to run Gump on top of Apache Harmony but it is currently not used. We expect to either start using it or give it back during the next quarter.

Project Branding Requirements

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 person with said skills.

The website now uses Forrest 0.9 which allowed us to remove our own custom skin that was only added in order to enable the trademark footer.


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

The time taken on vmgump has almost halfed when compared to last quarter mostly due to migrating to a new virtual host; it is now back where it used to be half a year ago. The time for the FreeBSD jail remains more or less the same.

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

Drafts/BoardReports/20110316 (last edited 2011-03-11 12:50:31 by StefanBodewig)