Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 38981 invoked from network); 25 Aug 2007 17:00:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Aug 2007 17:00:37 -0000 Received: (qmail 33939 invoked by uid 500); 25 Aug 2007 17:00:33 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 33877 invoked by uid 500); 25 Aug 2007 17:00:32 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 33868 invoked by uid 99); 25 Aug 2007 17:00:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Aug 2007 10:00:32 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of phil.steitz@gmail.com designates 64.233.182.191 as permitted sender) Received: from [64.233.182.191] (HELO nf-out-0910.google.com) (64.233.182.191) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Aug 2007 17:00:26 +0000 Received: by nf-out-0910.google.com with SMTP id d3so863678nfc for ; Sat, 25 Aug 2007 10:00:04 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cIrzFqZAUd+flM7ZxFHJpwviKXZt0NZKQZqGwuRk7omfL98lbUwY86wCPCFTmKQz6g6CklP1qxSYAdTWfzdH7riwH2EqvSHfMewe4LF2aou5nyiWfKUPzBnxh6B1Jn4SdFne6V6dzchPGj3wUkLlTWxF9hCWhH5jBl3bBqcpP1U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O1IOByd2qnTlfHntQ0oOpz30uK+4XhQLla1j//uVqWguAWE7Y8XgTVmSSJrWbvkZbx5ejclFxo30KC4V3L3Is3Y2bfp4kSIuZ6kXh+FHH3Ola9op/9Kxm3VK5QVA3kkqZG4b0MKIueUBbQzCoOncqsW2MviBdrG131U3g9z2Svc= Received: by 10.78.170.6 with SMTP id s6mr2612061hue.1188061204205; Sat, 25 Aug 2007 10:00:04 -0700 (PDT) Received: by 10.78.107.15 with HTTP; Sat, 25 Aug 2007 10:00:03 -0700 (PDT) Message-ID: <8a81b4af0708251000i7236fbd1t931d671a9ff28841@mail.gmail.com> Date: Sat, 25 Aug 2007 10:00:03 -0700 From: "Phil Steitz" To: "Jakarta Commons Developers List" Subject: Re: [all][poll] How should nigthlies / CI work? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <16d6c6200708250857r2100bee5g1d9533dab75a64c4@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 8/25/07, Noel J. Bergman wrote: > Martin Cooper wrote: > > > > GUMP builds are deemed non-trusted, since GUMP downloads from > > > non-ASF sites and includes them in builds without any vetting > > > of the third party dependencies. > > > True, but it's not clear that everything in the public Maven repo > > should be considered as "vetted" either. > > Exactly. Maven continues to be remiss in delivering on their goal of > ensuring authenticated packages. I view anyone who uses the public Maven > repository as being foolish; competent Maven users have their own private > repositories. > > And, yes, the corollary that GUMP is building from the latest of everything > is another key reason not to use it for nightly builds. > Another reason is that it is a little easier for us to manage "publication" of the CI artifacts using Continuum / vmbuild. We can publish both jars and zips/tarballs to a local maven repo on vmbuild and set up rsynch to people.apache.org, eliminating some of the ugliness in the bash setup. So can I get some feedback on the "what to publish" question? 1. Most recent successful build only 2. A stack of the n (probably = 5) most recent successful builds I guess if we really want to hold on to the "nightly" idea, we could do 3. Symlink nightly the subset of 2 that correspond to the last n nights. 3. gets us back into bash/cron more deeply. 1. is bash/cron free (other than rsynch) and 2. requires cron cleanup. All are simpler than the current bash script, though. I am happy help implement any of these. Phil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org