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.
A new Gump instance running on Mac OS X, Some development that lead to support for Maven 3.x, work on project branding requirements, 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 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.
In November we've been told that somebody was running Gump on top of OpenJDK7 and encountered some compatibility issues - which is no surpise, we've always seen problems when we upgraded Java versions. One of the issues identified led to changes inside Ant's trunk to work around backwards incompatible changes in javac. Unfortunately the results of said Gump installation do not seem to be available to the public.
Gump now supports Maven 3.x as a builder.
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.
Sander Temme installed Gump on an XServe running Mac OS X Server. This installation is currently only running the small subset of projects we use for testing.
We've asked the infra team for a new VM to run Gump on top of Apache Harmony. Mark Hindess of the Harmony community volunteered to help with the Harmony side of things.
Project Branding Requirements
Project Website Basics
The Gump website matched the requiremens ever since Gump became a TLP.
Project Naming And Descriptions
Many pages only referred to "Gump" - this has been fixed. The home page starts with a description and there is no download page.
Website Navigation Links
We had to add a link to www.apache.org and the security link. Our license link points to the 2.0 license directly.
The requirements are met now.
Logos and Graphics
Logos still need a "TM" symbol, waiting for somebody with the skills required to make the change.
It would be good if there was any (at least one) logo to take inspiration (or steal the typography of "TM") from, but even the feather at www.apache.org lacks the required "TM" as of this writing.
Has been in place already.
As of Wed, 8 Dec 2010 the ASF installations check out a bit less than 190 source trees (119 from the ASF repository) and try to build a bit more than 700 "projects". A complete Gump run takes more than sixteen hours on vmgump and seven and a half on the FreeBSD jail.
The time taken on vmgump has almost doubled when compared to last quarter while it remains more or less constant on the FreeBSD jail. Given that we don't have significantly more failures on FreeBSD the difference is likely related to other things that happen in parallel on the machines hosting the VM/jail.