Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73608 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37974 invoked from network); 6 Apr 2014 01:40:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Apr 2014 01:40:52 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.107 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.107 smtp107.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.107] ([108.166.43.107:45143] helo=smtp107.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 50/50-35101-2A0B0435 for ; Sat, 05 Apr 2014 20:40:51 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 61EDB987AA; Sat, 5 Apr 2014 21:40:48 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 096D6982FB; Sat, 5 Apr 2014 21:40:47 -0400 (EDT) Message-ID: <5340B09F.6040807@sugarcrm.com> Date: Sat, 05 Apr 2014 18:40:47 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Nikita Popov CC: PHP Internals References: <53404E5E.6010109@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Travis CI unit tests From: smalyshev@sugarcrm.com (Stas Malyshev) 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? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227