Mailing-List: contact general-help@gump.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Gump code and data" <general@gump.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
From: Stefan Bodewig <bodewig@apache.org>
To: general@gump.apache.org
Subject: [REPORT] Gump Board Report Q2 2010
Date: Mon, 14 Jun 2010 05:55:30 +0200
Message-ID: <87631mmfnx.fsf@v35516.1blu.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

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.

== Issues ==

There are no Board level issues.

== Community ==

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.

== Development ==

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.

== Releases ==

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.

== Infrastructure ==

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

== Statistics ==

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 http://vmgump.apache.org/gump/public/ and a
    Solaris zone at http://gump.zones.apache.org/gump/test/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org