Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55270
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E66C906.7060402@sugarcrm.com>
References: <4E66C906.7060402@sugarcrm.com>
Date: Wed, 7 Sep 2011 03:53:24 +0200
Message-ID: <CAH-PCH7fTzkrLWEqvJ++0C_KuFADqNaF3CK9oJh-J8AjL68A3w@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: tyra3l@gmail.com (Ferenc Kovacs)

On Wed, Sep 7, 2011 at 3:29 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrot=
e:
> 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
>
>

Hi, I also support the idea.
I would suggest setting up a jenkins(ex-hudson) cluster, it is the
leading CI product on the market (and a really successful open source
project), and it is really well-known in the php community as well,
and because I have used for my other projects in the past(not just for
php, but for some C apps also).
Jenkins supports having multiple slave instances running on different
platforms, nicely bound together, so you only access the master
instance through your browser, but the builds itself can be off-loaded
to the slaves (
https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds ).
I would be happy to help setting it up.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu