Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55268
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.153 as permitted sender)
Message-ID: <4E66C906.7060402@sugarcrm.com>
Date: Tue, 06 Sep 2011 18:29:42 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: CI for 5.4
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

Since we started to pay real attention to our unit tests now, I wonder 
if we could set up some kind of frequently-running CI system that could 
be used to screen commits and identify breakage early? That'd help with 
5.4 process I think.
We have http://gcov.php.net/ but it doesn't run with the frequency I'd 
like and since it says the run takes 44 hours it's kind of 
understandable. So I wonder if we could have something that just builds 
it and runs unit tests and we could see it in the same format as on 
gcov? Ideally after each commit would be nice, but say once an hour or 
two (even fullest unit tests run should take more than that, I think) 
would be OK too. If we could have two of them, like Linux & Windows, 
it'd be even better, but at least one would be nice.
What do you think?
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227