Newsgroups: php.internals,php.qa
Path: news.php.net
Xref: news.php.net php.internals:56034 php.qa:65937
Return-Path: <tyra3l@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 84772 invoked from network); 3 Nov 2011 17:04:32 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 3 Nov 2011 17:04:32 -0000
Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
X-PHP-List-Original-Sender: tyra3l@gmail.com
X-Host-Fingerprint: 209.85.213.42 mail-yw0-f42.google.com  
Received: from [209.85.213.42] ([209.85.213.42:59868] helo=mail-yw0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id EC/15-50864-E99C2BE4 for <internals@lists.php.net>; Thu, 03 Nov 2011 12:04:31 -0500
Received: by ywb26 with SMTP id 26so1698308ywb.29
        for <multiple recipients>; Thu, 03 Nov 2011 10:04:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=HZv+LwI3klDb7myTtQv1dgge5tlbJwbOVDTybs+2jcM=;
        b=I5U95pFJ4qKLaIZ/EVUozd1UFAqqi9keOeLzrjkQ4qdqKYR49M0mQOhyVzamoOwXzP
         /t2OR7hGZ1xQGdmYjDT6BiT6VtECcz4TVSRVyfR7Q0P8uZencFZTb08yMk1bhLMgS+rf
         zH0a7yb4zSAmbbyWJ2SviOYQg//Cbxi7ItlFw=
MIME-Version: 1.0
Received: by 10.150.114.8 with SMTP id m8mr10242420ybc.19.1320339867465; Thu,
 03 Nov 2011 10:04:27 -0700 (PDT)
Received: by 10.146.71.16 with HTTP; Thu, 3 Nov 2011 10:04:27 -0700 (PDT)
In-Reply-To: <CAH-PCH7_SKFckOYQt7vSJr063M9RA_zJGTGVc1Q+xjgW=hXu2Q@mail.gmail.com>
References: <4E66C906.7060402@sugarcrm.com>
	<CAH-PCH7fTzkrLWEqvJ++0C_KuFADqNaF3CK9oJh-J8AjL68A3w@mail.gmail.com>
	<CADNQb0XM1+Xn9peyv7uG3wZUz7WBNqOhcyyVmZKTADNXucfodw@mail.gmail.com>
	<CAH-PCH7_SKFckOYQt7vSJr063M9RA_zJGTGVc1Q+xjgW=hXu2Q@mail.gmail.com>
Date: Thu, 3 Nov 2011 18:04:27 +0100
Message-ID: <CAH-PCH5XdejMmO1d=LzupudsEQxT5rTw3ewPAKvcg9Pu7J9gGA@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>, PHP QA <php-qa@lists.php.net>
Content-Type: multipart/alternative; boundary=000e0cd4c13cc8779a04b0d7948d
Subject: Re: [PHP-DEV] CI for 5.4
From: tyra3l@gmail.com (Ferenc Kovacs)

--000e0cd4c13cc8779a04b0d7948d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 3, 2011 at 1:46 AM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

>
>
> On Wed, Sep 7, 2011 at 11:29 AM, Hannes Magnusson <
> hannes.magnusson@gmail.com> wrote:
>
>> On Wed, Sep 7, 2011 at 03:53, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>> > On Wed, Sep 7, 2011 at 3:29 AM, Stas Malyshev <smalyshev@sugarcrm.com>
>> wrote:
>> >> Hi!
>> >>
>> >> Since we started to pay real attention to our unit tests now, I wonde=
r
>> 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 r=
un
>> >> should take more than that, I think) would be OK too. If we could hav=
e
>> 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
>> >>
>> >> --
>> >> 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.
>>
>> We have wanted to setup some buildbots and testing environments for
>> years now, and I think we even have several boxes still laying around
>> for that purposes.
>> If you think you can handle the initial installation, go for it.
>> I'll see if I can hunt down the credentials somewhere.
>>
>> -Hannes
>>
>
> Hi.
>
> We ended up creating a Proof-of-concept  Jenkins installation using the
> server which was originally planned(
> https://wiki.php.net/internals/buildbot<https://wiki.php.net/internals/bu=
ildbot?s[]=3Dbuildbot> )
> to be used for the buildbot setup(obviously Hannes managed to get the
> credentials \o/), and created an RFC based on the current setup and the
> ways that it could be extended:
> https://wiki.php.net/rfc/jenkins
> Basically it continuously(when the are changes in SVN since the last
> build) builds our supported branches, runs the phpt testsuite(nicely
> integrated the test results with jenkins), and also executes the Symfony2
> phpunit testsuite for each branch.
> I think that using Jenkins would be really useful, as it is takes care of
> the "hard" part of the CI process(distributed build support, integration
> with every QA tool out there), and the php community is pretty much
> familiar with it (at least those who are knew what the CI acronym means)
> plus it is easy to integrate the userland testsuites, as many of those
> projects already using Jenkins or phpunit, which is nicely integrated wit=
h
> Jenkins, thanks to Sebastian.
>
> We knew that Pierre and Dan is working on a distributed build/test
> environment also, so we are well aware the fact that our work is maybe
> redundant, or could end up as wasted, but we thought that it still worth
> the effort.
>
> Please check out the RFC, and if you have any question or opinion on the
> matter, feel free to discuss in this thread.
> Oh, and of course check out http://ci.qa.php.net/
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>


A little update, I finished the master.php.net integration, so now you
should be able to login using your svn credentials.

ps: you can access the site using https, but it will use a self signed
cert, this can be fixed in the future, but unfortunately our
*.php.netwildcard cert won't work for
ci.qa.php.net :(

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--000e0cd4c13cc8779a04b0d7948d--