Newsgroups: php.internals,php.qa Path: news.php.net Xref: news.php.net php.internals:56045 php.qa:65942 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6522 invoked from network); 3 Nov 2011 19:17:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Nov 2011 19:17:11 -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.160.170 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:49245] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/29-50864-3B8E2BE4 for ; Thu, 03 Nov 2011 14:17:07 -0500 Received: by gyg13 with SMTP id 13so1834122gyg.29 for ; Thu, 03 Nov 2011 12:17:04 -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 :cc:content-type; bh=z7tgl6+CR0J34Poqlpqo+5UX/hWkCCsdLB5Y1L1Wh3Q=; b=q5YTq7tegQsebCA9OnEgulP4DOJe9lJ/Cu7mwV9zpiTwrpTZWj1R8nlHM9odE/PFc2 4xqM1f91vstDWDMdJLfJoG3exfTstOzuhWdTvY17rCHnPnaxRo0bzg75NIoJEHUfZSCU GnAsJDQCbziEUc89UeOPX+bjvj+9Iq4cX2fh0= MIME-Version: 1.0 Received: by 10.146.72.7 with SMTP id u7mr2625816yaa.9.1320347740173; Thu, 03 Nov 2011 12:15:40 -0700 (PDT) Received: by 10.146.71.16 with HTTP; Thu, 3 Nov 2011 12:15:39 -0700 (PDT) In-Reply-To: References: <4E66C906.7060402@sugarcrm.com> Date: Thu, 3 Nov 2011 20:15:39 +0100 Message-ID: To: Stefan Marr Cc: Klaus Silveira , PHP Internals , PHP QA Content-Type: multipart/alternative; boundary=000e0cd539b608766604b0d96aa9 Subject: Re: [PHP-DEV] CI for 5.4 From: tyra3l@gmail.com (Ferenc Kovacs) --000e0cd539b608766604b0d96aa9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Nov 3, 2011 at 7:43 PM, Stefan Marr 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 loca= l > setup was insufficient to catch it. > > Thanks a lot > Stefan > > It is, and as I mentioned in the RFC the email notification can be enabled 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, when to mail, etc.) and optionally you can notify the person whose commit break 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.qa on 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 who 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] :( --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --000e0cd539b608766604b0d96aa9--