Re: [REPOST] [GUMP] Cactus nightly builds

[Vincent Massol]

Thanks Bill. At least there is someone there ... :) Actually GUMP is a proposal that is part of the Alexandria project. GUMP is used to automatically create nightly builds for jakarta projects (you can check the status of each run on http://jakarta.apache.org/builds/gump/latest/) Cheers, Vincent. ----- Original Message ----- From: Bill Smith To: '[EMAIL PROTECTED]' Sent: Thursday, June 28, 2001 8:43 PM Subject: RE: [REPOST] [GUMP] Cactus nightly builds For what it's worth, I just received your email, and the only apache newsgroup that I subscribe to deals with alexandria, not GUMP.  Good luck finding an answer to your question.   Best Regards, Bill Smith -----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 28, 2001 2:39 PM To: [EMAIL PROTECTED] Subject: [REPOST] [GUMP] Cactus nightly builds Hi there,   Can someone help me on this ? This is the third time I am posting with no answer whatsoever !! Should I assume that either this project is dead or noone cares about GUMP ? Even if you're busy can you at least spare me a few words explaining the status ... :)   Thanks for your time. Vincent   P.S.: I am actually a bit angry as I am trying to progress on the subject of nightly builds since the 15 of march 2001 ... with very little progress ! I don't care about doing the work myself if you give me the correct privileges.   -------------   Hi all, [I'm not sure this is the correct newsgroup for GUMP. Tell me if it is not !] I'd like to progress on the gumpization of Cactus and especially in the generation of nightly builds. We are at a stage where we are now in much need of nightly builds ! The questions are : How can we progress on this subject ? Can I help ? Who can help (Sam ?) ? On what machine GUMP builds are run ? Is there any servlet engine (Tomcat 3.x, Tomcat 4.x, ...) installed on that machine so that we could run functional tests as well during the build ? In term of GUMP integration, Cactus Ant build scripts have 3 targets that might be interesting : - "tests", run all tests on selected servlet engines (selection is done by editing a build.properties file at the same location as build.xml) - "dist", run everything except the tests and packages the distibution files. There are 3 output files that would need to be copied to the /www/jakarta.apache.org/builds/jakarta-commons/nightly/commons-cactus/<date of build>. Files are : commons-cactus-22-<date>.zip, commons-cactus-23-<date>.zip and commons-cactus-src-<date>.zip - "all" : does it all : dist + tests So really, the one that we should strive to run is "all" as one of the most powerful feature of nightly builds is to be able to daily exercise the tests ... Thanks for your help. Vincent. [Cactus committer]