Gump Board Report Draft
Hi all the current draft is at https://cwiki.apache.org/confluence/display/GUMP/20201216 - basically the same report as usual, pointing out the VM migration as real activity. I'm going to send the report during the coming Wednesday. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump Board Report Draft
> On Sep 3, 2016, at 8:24 AM, Stefan Bodewigwrote: > > as usual, feel free to modify it as needed. I'll submit it around the > next weekend > > https://wiki.apache.org/gump/Drafts/BoardReports/20160921 +1 > Thanks > >Stefan > > - > To unsubscribe, e-mail: general-unsubscr...@gump.apache.org > For additional commands, e-mail: general-h...@gump.apache.org > -- san...@temme.net http://www.temme.net/sander/ PGP FP: BCD1 6D2C 8906 C48A 540E 253E 94D3 36A3 6D15 930A signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Gump Board Report Draft
On 2016-09-06, Martin van den Bemt wrote: > "installation will ge puppetized" should probably be "installation > will get puppetized" right, thanks Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump Board Report Draft
"installation will ge puppetized" should probably be "installation will get puppetized" Mvgr, Martin On Sat, Sep 3, 2016 at 5:24 PM, Stefan Bodewigwrote: > as usual, feel free to modify it as needed. I'll submit it around the > next weekend > > https://wiki.apache.org/gump/Drafts/BoardReports/20160921 > > Thanks > > Stefan > > - > To unsubscribe, e-mail: general-unsubscr...@gump.apache.org > For additional commands, e-mail: general-h...@gump.apache.org > - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Draft
as usual, feel free to modify it as needed. I'll submit it around the next weekend https://wiki.apache.org/gump/Drafts/BoardReports/20160921 Thanks Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report
Hi all I've started a "nothing happened, things are chugging along" report at https://wiki.apache.org/gump/Drafts/BoardReports/20160316 Feel free to add stuff if I missed anything. Cheers Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report
Hi all a bit late this time, will send the report by Wednesday, please add/correct as needed: https://wiki.apache.org/gump/Drafts/BoardReports/20140618 Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Q4/2013
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 ASF as well as non-ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and XMLUnit.NET. == Summary == Very little activity, Gump seems to create useful results for the few projects that use it. A team at Oracle seems to be running Gump for compatibility tests of Java 8. == Releases == Gump has never done any releases. One reason for this is that the ASF installations of Gump work on the latest code base almost all of the time following its integrate everything continuosly philosophy. Stefan has polled the Gump list and our only known user outside of the ASF whether anybody would like to see a release but no response was received. == Activity == Ludmila Shikhvarg who works at Oracle and tests next-Java compatibility runs Gump internally at Oracle. Unfortunately the instance is not a public one. Occasionally she pings the Gump list to tells us about build problems she sees, she did so for three projects and Java8 in October and traffic has been directed to the project mailing lists. The Gump installation on vmgump was stuck for several weeks and nobody noticed it. == 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. The most recent addition to the PMC was in December 2006 when we added Sander Temme. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Q4 2012
Hi all, I'm sorry but this time I didn't manage to create the (copy-pasted either way) Wiki page for the report and am late, below is what I posted: 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. == Summary == No Board level issues. == 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. == Activity == This has been a very quite month even by Gump's standard. Very few tweaks have been made to metadata and not a single commit to the code base. == 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. == Statistics == As of Tue, 11 Dec 2012 the ASF installations check out a bit less than 175 source trees (114 from the ASF repository) and try to build a bit more than 850 projects. A complete Gump run takes about ten hours on vmgump and about eight on the FreeBSD jail and nine and a half on Adam where more projects fail to build. [1] the main instance at http://vmgump.apache.org/gump/public/ , a FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS X Server at http://adam.apache.org/gump/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Q1 2012
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. == Summary == No Board level issues. == 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 == The site now uses svnpubsub. If we ever want to create a release, we'll use svnpubsub right from the start. We encountered only a few minor hickups after the upgrade to FreeBSD 9.0, mostly due to upgrading svn and having to upgrade all working copies. Many thanks to the infra team. == Activity == 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. During this quarter we've tweaked git support to allow pulling from branches other than master. There are 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. We've finally given up waiting for expat to build on libtool2 systems and now provide a system installed expat, this means we've started to sucessfully build APR and projects depending on APR for the first time since at least a year, probably longer. == 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. == Branding and Naming == We believe to meet all branding requirements. == Statistics == As of Tue, 13 Mar 2012 the ASF installations check out a bit less than 180 source trees (115 from the ASF repository) and try to build a bit more than 850 projects. A complete Gump run takes about nine and a half hours on vmgump and about nine on the FreeBSD jail and ten on Adam where more projects fail to build. [1] the main instance at http://vmgump.apache.org/gump/public/ , a FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS X Server at http://adam.apache.org/gump/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Q3 2011
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. == Summary == No development activity at all, no issues. == 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. The past quarter several projects built by Gump have been moved to the Attic and now are no longer built by Gump, the only notable addition is the Tomcat 7 branch. == Development == None. == 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 == No new is good news. == Project Branding Requirements == We believe to meet all requirements by now. == Statistics == As of Sat, 17 Sep 2011 the ASF installations check out a bit more than 170 source trees (114 from the ASF repository) and try to build a bit less than 800 projects. A complete Gump run takes about eight hours on vmgump. Timings for the FreeBSD jail and the MacOS X server are currently not available as either build is having issues. Some builds have been removed since the projects moved to the Attic (Cactus, for example). [1] the main instance at http://vmgump.apache.org/gump/public/ , a FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS X Server at http://adam.apache.org/gump/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Q1 2011
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. == Summary == Low development activity to adapt to a difference between mvn 2.x and 3.x, the Mac OS X machine went live, no issues. == 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. Support requests for the non-public Gump installation running on top of OpenJDK7 dribble in and get addressed. == Development == Only minor changes that lead to separate install builders for mvn2 and mvn3. == 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 == 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. == Statistics == 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 http://vmgump.apache.org/gump/public/ , a FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS X Server at http://adam.apache.org/gump/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Q4 2010
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. == Summary == 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. == 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. In November we've been told that somebody was running Gump on top of OpenJDK7 and encountered some compatibility issues[2] - 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. == Development == Gump now supports Maven 3.x as a builder. == 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 == 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. === Trademark Attributions === 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. === Project Metadata === Has been in place already. == Statistics == 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. [1] the main instance at http://vmgump.apache.org/gump/public/ , a FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS X Server at http://adam.apache.org/gump/ [2] http://mail-archives.apache.org/mod_mbox/gump-general/201011.mbox/%3c4cd8a848.4000...@oracle.com%3e - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[REPORT] Gump Board Report Q2 2010
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-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[REPORT] Gump Board Report for Q3 2009
Infrastructure: * many thanks to the infra team for upgrading the OS on vmgump. Technical: * the installation is chugging along with active metadata maintenance. Excalibur moving to Maven 2 builds and Tomcat restructuring its svn tree caused a few hickups that have been resolved by now. Other: * still all Apache committers have access to metadata in svn. * no releases. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump Board Report Q3 2008
No surprises here ... Infrastructure: * no news is good news. Technical: * the installation is happily chugging along but no active development Other: * still all Apache committers have access to metadata in svn. * no releases. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache Gump Board Report
Infrastructure: * no new is good news. Technical: * the installation is happily chugging along but no active development Other: * still all Apache committers have access to metadata in svn. * no releases. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache Gump Board Report
No news :) Mvgr, Martin Stefan Bodewig wrote: Infrastructure: * no new is good news. Technical: * the installation is happily chugging along but no active development Other: * still all Apache committers have access to metadata in svn. * no releases. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache Gump Board Report
On Mon, 16 Jun 2008, Martin van den Bemt [EMAIL PROTECTED] wrote: No news :) I know. Since we do have Maven2 support working well enough I've turned to other stuff again. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Gump Board Report 03/2007
Infrastructure: * Justin was kind enough to bring vmgump's Debian packages up to more recent versions, many thanks. * vmgump probably is at its limits of disk space as well as CPU. A full run of what we currently build is taking more than 6 and a half hours. Technical: * vmgump is now running Mono 1.2.3 and successfully builds NAnt. The next step is making Gump's NAnt support actually work and start building log4net. Other: * still all Apache committers have access to metadata in svn. * no releases. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]