From continuum-dev-return-5601-apmail-maven-continuum-dev-archive=maven.apache.org@maven.apache.org Mon Jan 15 12:11:15 2007 Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 55990 invoked from network); 15 Jan 2007 12:11:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jan 2007 12:11:14 -0000 Received: (qmail 86760 invoked by uid 500); 15 Jan 2007 12:11:20 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 86736 invoked by uid 500); 15 Jan 2007 12:11:20 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 86725 invoked by uid 99); 15 Jan 2007 12:11:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jan 2007 04:11:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [193.19.64.142] (HELO ow-mustang.objectware.no) (193.19.64.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jan 2007 04:11:11 -0800 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by ow-mustang.objectware.no (8.12.11.20060308/8.12.11) with ESMTP id l0FC8HUv012748 for ; Mon, 15 Jan 2007 13:08:18 +0100 Message-ID: <45AB6D65.9020500@apache.org> Date: Mon, 15 Jan 2007 13:02:45 +0100 From: =?ISO-8859-1?Q?Trygve_Laugst=F8l?= User-Agent: Thunderbird 2.0b1 (X11/20061228) MIME-Version: 1.0 To: continuum-dev@maven.apache.org Subject: Re: Trusting in our own dog food References: <8538DDFC-1E7D-4C3F-86AF-260D5E626C79@apache.org> <45A5FBF1.2020807@apache.org> <02CBD975-4D40-47E7-9B53-1700C7E89A90@apache.org> In-Reply-To: <02CBD975-4D40-47E7-9B53-1700C7E89A90@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Brett Porter wrote: > so... you're saying you don't trust our dog food? :) No, I'm saying it's there to verify the dog food. If there is no discrepancies between what the cron is saying and the C instance is saying, it's good. If there is an discrepancy it's not good. It will be more a tool to verification tool that a CI (but that might be two sides of the same story :) -- Trygve > > The only thing it tests differently is: > - works by cron, whereas continuum might go down/hang/something else > (which is something we should work on fixing if it does, rather than > rely on ci.sh) > - runs a reactor (can add that as a less frequent build execution in > continuum too, though). > > So, I don't see any reason to keep it - wdyt? > > - Brett > > On 11/01/2007, at 7:57 PM, Trygve Laugstøl wrote: > >> Brett Porter wrote: >>> Folks, >>> I'd like to turn off continuum_ci.sh and instead only use Continuum >>> itself to do CI for Continuum. Any objections? >> >> I don't see why it should be turned off, but perhaps the automatic >> notifications can be turned off or just send failures. That way it >> would verify the product (it will in itself be an integration test) >> because if the Continuum instance says that something is failing, you >> should expect an email saying the same right after. Or at least you >> can check the logs directory if you're suspecting some other failure. >> >> -- >> Trygve