|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|'''This report has been sent'''
This report has been sent
Apache Gump is a cross-project continuous integration server. 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 Board level issues.
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.
Since early this year our self-written maven repository proxy faces random hangs when requesting artifacts from the central Maven repository which leads to build processes being killed after the timeout of one hour. As a result Gump runs currently take several days and we disabled nag emails as build failures were more often related to this problem than a change in the project itself. The underlying problem hasn't been fully analyzed so far.
The dataset of projects built by Gump is maintained by only a few people contributing across all projects and a few additional people maintaining the metadata of the projects they are interested in the most.
The Mac OS X server usually running Gump, adam.apache.org, has undergone an OS upgrade. The Gump installation is awaiting restoration.
Changes to the Roster
All ASF committers have write access to the metadata that configure the ASF installations.
No new committers to the code base, no changes to the PMC.