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.


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.


The last quarter has seen a minor improvement that allows output file names to be specified with wildcards. Since Gump cannot influence the names of jars created by Maven 2.x the paths had to be adjusted with every release of a project built by it so far.

We've managed to build a few projects that have been failing for a long time in Gump - among them the ASF projects Portals, ActiveMQ, Directory Server, Tapestry and parts of Camel.


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.


Access to vmgump has been tightened up, the number of people with sudo has been reduced and OPIE is now required.


As of Sun, 06 Jun 2010 the ASF installations check out a bit less than 200 source trees (114 from the ASF repository) and try to build a bit more than 600 "projects". A complete Gump run takes more than eleven hours on vmgump and eight and a half on the Solaris zone.

[1] the main instance at and a Solaris zone at

Drafts/BoardReports/20100616 (last edited 2010-06-14 03:56:07 by StefanBodewig)