Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73703
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.169 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <534D5F7F.5080604@sugarcrm.com>
References: <534C2133.8010402@sugarcrm.com> <CAMUwpuQ495nqk08Se1oKC5bpsNSBBVyAyi+uNtPctbsC+sDAtA@mail.gmail.com>
 <534D5F7F.5080604@sugarcrm.com>
Date: Tue, 15 Apr 2014 18:36:50 +0200
Message-ID: <CAMUwpuQ3n99PvNN06YaPPtFO9BDvSN_M0T63nwmK_9DxkFfrEQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] keeping unit tests green
From: jpauli@php.net (Julien Pauli)

On Tue, Apr 15, 2014 at 6:34 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> So I'm OK, as soon as it is simple.
>> For example, I dont know Travis. So when opening the Travis page about
>> PHP, I see many things, red or green, and feel like lost in all those
>> informations.
>
> Travis is pretty simple as such - you go to
> https://travis-ci.org/php/php-src/builds and check out your branch
> (branch name is in Commit column). If it's not green, you click on the
> build number and get the log which says what went wrong. The failed
> tests are usually at the very end, and once you know the names of the
> tests failed, look them up in the log to find the details.
>
> With pulls on github, you just click on "Details" link and it gets you
> to the same log page.
>
> Setting up a fork requires some configs, but Travis docs are good
> enough. I might also add a wiki page on how to set up the fork in Travis
> a bit later.

Yes I spent some time to see how it works, it seems pretty easy.

In fact, if we could add more analyze tools, it would be nice, because
actually, it just acts as an autommated "make test".


Julien