Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56089
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 20282 invoked from network); 7 Nov 2011 10:14:53 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 7 Nov 2011 10:14:53 -0000
Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; 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:60877] helo=mail-yw0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 27/E0-03509-B9FA7BE4 for <internals@lists.php.net>; Mon, 07 Nov 2011 05:14:51 -0500
Received: by ywb26 with SMTP id 26so5710822ywb.29
        for <multiple recipients>; Mon, 07 Nov 2011 02:14:48 -0800 (PST)
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
         :cc:content-type;
        bh=6ME+AwtJSnaIEAyfZrTjTzWWAoGLZEHlrTZX0RYu2Cw=;
        b=TNtNhp9TFTZoxA1lg9TT+x0ecxzl/mOTIz3lTeDJQDr1w5+B3bdH78mosD3LWpTWcM
         /oVdJ6ZLnvhHQ0BPvIzHaIIVPYT9Puh/xrmryyCtkAO7PPqZRGc4Kqf1BHHsc7eJcawQ
         Vn6ot+26hO5j1OAqTV6DbZ8YCQ+9LStExpd9E=
MIME-Version: 1.0
Received: by 10.236.23.67 with SMTP id u43mr33302118yhu.123.1320660888126;
 Mon, 07 Nov 2011 02:14:48 -0800 (PST)
Received: by 10.146.71.16 with HTTP; Mon, 7 Nov 2011 02:14:48 -0800 (PST)
In-Reply-To: <CAH-PCH4EU5V02kwQ4O_Yrd5qhudjqaztKxjM=m7GnrCyh89wAA@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>
	<CAH-PCH5XdejMmO1d=LzupudsEQxT5rTw3ewPAKvcg9Pu7J9gGA@mail.gmail.com>
	<CAFst3WqTzSExTUK-KUoPgvL7djfr3A4_sd4GgmLJvakcpWy+_w@mail.gmail.com>
	<CAH-PCH5fT4nknjyjqN4=Shp0dPiadZGg0mafOaX93qeDTgiSGQ@mail.gmail.com>
	<F59ECA58-A69F-4DEE-8A47-41E3E71D2B9C@stefan-marr.de>
	<CAH-PCH4EU5V02kwQ4O_Yrd5qhudjqaztKxjM=m7GnrCyh89wAA@mail.gmail.com>
Date: Mon, 7 Nov 2011 11:14:48 +0100
Message-ID: <CAH-PCH4aRFZ5ggLyBqDR_aOn-GmoocjxH8C_GcSC6okb0_xopA@mail.gmail.com>
To: Stefan Marr <php@stefan-marr.de>
Cc: Klaus Silveira <contato@klaussilveira.com>, PHP Internals <internals@lists.php.net>, 
	PHP QA <php-qa@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8f5034a41b0c1a04b12253c4
Subject: Re: [PHP-DEV] CI for 5.4
From: tyra3l@gmail.com (Ferenc Kovacs)

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

On Thu, Nov 3, 2011 at 8:15 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

>
>
> On Thu, Nov 3, 2011 at 7:43 PM, Stefan Marr <php@stefan-marr.de> wrote:
>
>> Hi Ferenc:
>>
>> On 03 Nov 2011, at 19:01, Ferenc Kovacs wrote:
>>
>> > Of course there are ways to improve the current setup, I listed those
>> ideas
>> > at https://wiki.php.net/rfc/jenkins#future_plans
>>
>> Very nice.
>> I don't know Jenkins, but would it be possible to mail the author of a
>> change in case it breaks something? I just had such a case, where my loc=
al
>> setup was insufficient to catch it.
>>
>> Thanks a lot
>> Stefan
>>
>>
> It is, and as I mentioned in the RFC the email notification can be enable=
d
> when needed, I didn't wanted to do that before introducing the RFC.
> There is a slight problem however: if we don't build each and every
> revision (which can happen, if two commit happens before the build starts=
,
> which can happen more easily if another build is in progress for that job=
,
> because then jenkins will just queue the build, not execute it right away
> for obvious reasons), so there is a slight chance for "blaming" the wrong
> person.
> The usual setup is that you have a mailing list/alias which always gets a
> mail about the build results (which can also be customized in detail, whe=
n
> to mail, etc.) and optionally you can notify the person whose commit brea=
k
> the build.
>
> As Klaus pointed out, there are other possibilities for notification,
> currently we were using the irc plugin, so if you hang around on #php.qao=
n efnet, you could see the build results or ask phpcibot about the status
> of the builds, However I just noticed that there is no way to restrict wh=
o
> can start builds through the irc bot(see
> https://issues.jenkins-ci.org/browse/JENKINS-5931), so I turned it off.
>
> 20:13 -!- phpcibot [~PircBotX@80.82.121.132] has quit [Remote host closed
> the connection]
>
> :(
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>

I reported https://issues.jenkins-ci.org/browse/JENKINS-11606 on the
jenkins issue tracker, and they fixed it super fast, so phpcibot is back
again. \o/


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

--e89a8f5034a41b0c1a04b12253c4--