Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55269
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
Sender: laruence@gmail.com
In-Reply-To: <4E66C906.7060402@sugarcrm.com>
References: <4E66C906.7060402@sugarcrm.com>
Date: Wed, 7 Sep 2011 09:34:24 +0800
Message-ID: <CABBJUpeKQdLKmmo8rz_FKsuLvMrnPaPTwxqD7tREUHwu7Nndcg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] CI for 5.4
From: laruence@php.net (Laruence)

+1

thanks

2011/9/7 Stas Malyshev <smalyshev@sugarcrm.com>:
> 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 li=
ke
> 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 com=
mit
> 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 tw=
o
> of them, like Linux & Windows, it'd be even better, but at least one woul=
d
> be nice.
> What do you think?
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
Laruence =C2=A0Xinchen Hui
http://www.laruence.com/