Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73610
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5340B09F.6040807@sugarcrm.com>
References: <53404E5E.6010109@sugarcrm.com>
	<CAF+90c811ZUSPcNZ7UiU=t2i+d5+-ezgppv1627cG+5v81-86w@mail.gmail.com>
	<5340B09F.6040807@sugarcrm.com>
Date: Sun, 6 Apr 2014 05:09:56 +0200
Message-ID: <CAEZPtU4frMHT0gtQHcJsCVW1hTWJ+0noGxcL18XJygQN3Ds_CA@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Travis CI unit tests
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Sun, Apr 6, 2014 at 3:40 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> It would be a good start to send a mail to the person introducing a CI
>> build failure automatically. I think to the most part people are simply
>> not aware that they introduce failures - it's not like anybody goes on
>> travis half an hour after doing a commit to check whether everything
>> works fine. Maybe bugging people about this is already enough to keep a
>> green build most of the time?
>
> Travis seems to have a way to do this:
> http://docs.travis-ci.com/user/notifications/#Email-notifications
>
> Maybe we should start with enabling it for on_failure: change and send
> the email to php-cvs list?

to internals, that's where discussions are supposed to happen. And if
one fears the spam, then we he will be motivated enough to keep it all
green :)

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org