Newsgroups: php.internals,php.qa
Path: news.php.net
Xref: news.php.net php.internals:56059 php.qa:65956
Return-Path: <tyra3l@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 44333 invoked from network); 3 Nov 2011 23:12:21 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 3 Nov 2011 23:12:21 -0000
Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
X-PHP-List-Original-Sender: tyra3l@gmail.com
X-Host-Fingerprint: 209.85.213.42 mail-yw0-f42.google.com  
Received: from [209.85.213.42] ([209.85.213.42:44061] helo=mail-yw0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id F0/50-50864-3DF13BE4 for <internals@lists.php.net>; Thu, 03 Nov 2011 18:12:20 -0500
Received: by ywb26 with SMTP id 26so2051161ywb.29
        for <multiple recipients>; Thu, 03 Nov 2011 16:12:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=xwDer6vQpUXDf5DsnTLYc3zpuSDdqgm/tZN1AXXw+5A=;
        b=aviUzUW7gjQlk58eqAP50oLR/ExYm2KTcW4fIW0k3HwTHud6GMHYaAUoW3uJdEYMZy
         Y1qq5HQc9wm6gAvN/QgXx9Ahl5JN7xiQBQji1mK6fJZFhj+H7K1Q9OITOem3QJ3s1+tL
         voZolHx7JlY43YJXxj8cBHDlWQRsBSyAsAUBQ=
MIME-Version: 1.0
Received: by 10.236.170.201 with SMTP id p49mr5666501yhl.106.1320361936113;
 Thu, 03 Nov 2011 16:12:16 -0700 (PDT)
Received: by 10.146.71.16 with HTTP; Thu, 3 Nov 2011 16:12:16 -0700 (PDT)
In-Reply-To: <4EB31CA7.6080008@lerdorf.com>
References: <4E66C906.7060402@sugarcrm.com>
	<CADNQb0XM1+Xn9peyv7uG3wZUz7WBNqOhcyyVmZKTADNXucfodw@mail.gmail.com>
	<CAH-PCH7_SKFckOYQt7vSJr063M9RA_zJGTGVc1Q+xjgW=hXu2Q@mail.gmail.com>
	<CAH-PCH5XdejMmO1d=LzupudsEQxT5rTw3ewPAKvcg9Pu7J9gGA@mail.gmail.com>
	<CAFst3WqTzSExTUK-KUoPgvL7djfr3A4_sd4GgmLJvakcpWy+_w@mail.gmail.com>
	<CAH-PCH5fT4nknjyjqN4=Shp0dPiadZGg0mafOaX93qeDTgiSGQ@mail.gmail.com>
	<F59ECA58-A69F-4DEE-8A47-41E3E71D2B9C@stefan-marr.de>
	<CAH-PCH4EU5V02kwQ4O_Yrd5qhudjqaztKxjM=m7GnrCyh89wAA@mail.gmail.com>
	<02FCF0AC-207E-4783-B590-E1F8150BD0E6@stefan-marr.de>
	<CAFst3WpbPKufEtJ60oCanz4dyCvG0HS-Fkie3E8ofv+=L4QDrw@mail.gmail.com>
	<CAH-PCH5J=m-9d-JiT3khrWQJTiRyYg-NSuzfUBSbBO=M2uZutg@mail.gmail.com>
	<CA+5g0SKjzshJdrKhcLkyYc3=wE830aPoSkHZWXTjvuU6rvfftA@mail.gmail.com>
	<CAH-PCH5d-2Dy03LC0aRy0dv6W2VWTxj7+ME9wqSko3qpYG1k1Q@mail.gmail.com>
	<4EB316C2.3050000@lerdorf.com>
	<CAH-PCH4sWeHvWKiuEVjrCChgKFt6gHVxgPzcEwfbRY03TAuxnA@mail.gmail.com>
	<4EB31CA7.6080008@lerdorf.com>
Date: Fri, 4 Nov 2011 00:12:16 +0100
Message-ID: <CAH-PCH7ZQ4GftOgOzvc3U=MQNRg1pUipK1qXY9p0QRo3QzYOLA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Felipe Pena <felipensp@gmail.com>, Klaus Silveira <contato@klaussilveira.com>, 
	Stefan Marr <php@stefan-marr.de>, PHP Internals <internals@lists.php.net>, 
	PHP QA <php-qa@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf305640c92d4ece04b0dcb8c5
Subject: Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] CI for 5.4
From: tyra3l@gmail.com (Ferenc Kovacs)

--20cf305640c92d4ece04b0dcb8c5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 3, 2011 at 11:58 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 11/03/2011 03:47 PM, Ferenc Kovacs wrote:
> > A, it will report every test failure, but we fix all of our tests so we
> > are cool. (my preference)
>
> But even if we do that, when a test does fail, it may take a couple of
> days to fix it. It would be nice if we didn't get an internals email for
> every commit that triggers a build during that time. So even in this
> ideal case I think the notification mechanism needs to be smarter.
>
> -Rasmus
>

using the email-ext plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin one can bind
email notification on the following events:
- Failure
- Unstable
- Still-Failing
- Success
- Fixed
- Still-Unstable
- (Before-Build)

So we could configure to only send emails on Failure and Fixed(I ignored
the Unstable on purpose for the sake of simplicity, of course we also use
this for option C).
That way we would only see the notification on the first error, and the
next mail would be when we finally fixed it.
This is still suboptimal, as we wouldn't get email notifications about the
other test failures introduced between the first failure and the fix, but I
think that having a failed build would mean that somebody/everybody is
working on fixing the build, so those test failures would also be
spotted(on the web interface) and fixed (without that, the build won't
succeed).

I almost forget to mention, but the email notification also supports
defining different recipients for each event, so for example the commiters
could still get the notification for each of their commits/builds until the
build is back to normal, that way the list wouldn't be spammed, but some
active contributors would be still continuously bugged.

How does it sounds to you?

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--20cf305640c92d4ece04b0dcb8c5--