Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45651
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.154 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=Pu/51SSpQxMO9F0np0wIyx7jyfKd8PjJ3Li2chbZCIyDqT2lHbib2TBex+zGVqW2DK
         Pj+jDqfE+b7fIdf3J67364N4E4iuojNGWs5dSvovKSXXiJo6Wk9mGpXi1FTrznXnyv07
         /l3nnt1k7ULyfhM3Fd5aROXQsuUCZ/KYG2rO0=
MIME-Version: 1.0
In-Reply-To: <7f3ed2c30909281055r45101f36k8c44bd8abb90dae7@mail.gmail.com>
References: <7f3ed2c30909261219i39ba6d0p9254b7d3e9e061c9@mail.gmail.com>
	 <d8b8d0160909262012x471d573ag57403b85c24e0d4@mail.gmail.com>
	 <7f3ed2c30909281055r45101f36k8c44bd8abb90dae7@mail.gmail.com>
Date: Wed, 30 Sep 2009 17:30:52 -0400
Message-ID: <d8b8d0160909301430n7023765drb34c27d9c4dc2611@mail.gmail.com>
To: Hannes Magnusson <hannes.magnusson@gmail.com>
Cc: Zoe Slattery <zoe@php.net>, systems@php.net, Scott MacVicar <scottmac@php.net>, 
	internals@lists.php.net
Content-Type: multipart/alternative; boundary=00c09ffb4c71d14d800474d23e00
Subject: Re: [PHP-DEV] Buildbot setup / do you want access to testing 
	platform?
From: israelekpo@gmail.com (Israel Ekpo)

--00c09ffb4c71d14d800474d23e00
Content-Type: text/plain; charset=UTF-8

On Mon, Sep 28, 2009 at 1:55 PM, Hannes Magnusson <
hannes.magnusson@gmail.com> wrote:

> First off, don't top-post :)
>
> On Sun, Sep 27, 2009 at 05:12, Israel Ekpo <israelekpo@gmail.com> wrote:
> > Hi Hannes,
> >
> > I want to help out.
> >
> > What do I have to do to set it up and what will be my responsibilities
> after
> > that.
>
> Your job would be to figure out the best way to do compile-testing on
> bunch of platforms, and run our test suite on those platforms
> (buildbot was the favorite of your predecessor, who unfortunately
> doesn't have the time right now). After having figuring that out you'd
> need to get it up and running on the various platforms (probably
> coordinating with Zoe, who knows the status of the run-tests
> 'framework' and could help you integrating the testing results in a
> readable manner).
>
> You would most definitely need to maintain the system for several
> years, so the better you are to help others understanding the system
> and sharing information the more chances you have of 'getting
> vacation' and piece & quite when you need it ;)
>
> So, are you up for the job soldier?
>
> -Hannes
>


Hi  Hannes,

Sorry for taking this long to respond.

1. I am ready for the challenge!

2. I would prefer to start with the Debian "lenny" server.

Most of my experience is with Ubuntu and CentOS.

Since Red Hat or CentOS is not one of the options, the Debian server will be
one that I am most comfortable with working with as it is the closest one to
Ubuntu.

3. After setting up the environment, I will attempt to replicate the set up
on the other servers listed here

http://wiki.php.net/internals/buildbot#operating_systems_available

FreeBSD 6.4 is available on 80.82.121.132
FreeBSD 7.2 is available on 80.82.121.133
Debian "lenny" is available on 80.82.121.134
OpenBSD 4.5 is available on 80.82.121.135
NetBSD 5.0 is available on 80.82.121.136

4. I am not really familiar with the buildbot process so I have some
questions .

By "test suites" and "run-tests" you are referring to the "make test" option
a developer has after compiling php, correct?

5. After setting up the environment successfully, I think the test results
should be formatted as XML for easy digest by humans and onward
transformation to other formats.

*How I plan to implement this :

1. I will set up a web service so that the a post commit hook from the
svn.php.net server can notify the build system immediately a commit is made
to the repository.

2. This notification will get dropped into a queue and the target revision
number will be checked out from SVN and compiled. Each revision number will
be compiled separately in sequence.

3. If the compilation fails, then the error messages will be captured. If it
passes, then the "test suite" will be applied.

4. The results will be captured and stored in the recommended format for
consumption later.

What do you think?*

-- 
"Good Enough" is not good enough.
To give anything less than your best is to sacrifice the gift.
Quality First. Measure Twice. Cut Once.

--00c09ffb4c71d14d800474d23e00--