Newsgroups: php.internals,php.qa Path: news.php.net Xref: news.php.net php.internals:56049 php.qa:65946 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14574 invoked from network); 3 Nov 2011 19:50:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Nov 2011 19:50:12 -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:52190] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 28/CA-50864-270F2BE4 for ; Thu, 03 Nov 2011 14:50:10 -0500 Received: by gyg13 with SMTP id 13so1866245gyg.29 for ; Thu, 03 Nov 2011 12:50:07 -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=3PhaWNfwTyXAXd6qsaXvzi5BUIQbmioAdkkfIf0uu6U=; b=WLsgEqNfo8nays2HfPHGwZWXS+7PURNIc01MRFjgjD248cVgftVER5cJvO4838LjLd 5C5UH47JS5T76WhhSR6UoazzaPcDdTRCRtYoFHojAXMOCcR4yd5xdiRtWi9N+9fHNwxB CXvj4sLspoPsudtJZy1EB7xvC3zhxAXmT3Sic= MIME-Version: 1.0 Received: by 10.146.72.7 with SMTP id u7mr2714336yaa.9.1320349795426; Thu, 03 Nov 2011 12:49:55 -0700 (PDT) Received: by 10.146.71.16 with HTTP; Thu, 3 Nov 2011 12:49:55 -0700 (PDT) In-Reply-To: References: <4E66C906.7060402@sugarcrm.com> <02FCF0AC-207E-4783-B590-E1F8150BD0E6@stefan-marr.de> Date: Thu, 3 Nov 2011 20:49:55 +0100 Message-ID: To: Klaus Silveira Cc: Stefan Marr , PHP Internals , PHP QA Content-Type: multipart/alternative; boundary=000e0cd539b68923ab04b0d9e4f4 Subject: Re: [PHP-DEV] CI for 5.4 From: tyra3l@gmail.com (Ferenc Kovacs) --000e0cd539b68923ab04b0d9e4f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Nov 3, 2011 at 8:41 PM, Klaus Silveira w= rote: > That's kind of a general setup, Stefan. Sending an email to the commiter > that broke the build with details of the build process, as well sending a= n > email to a mailing list. > > I'll be looking into this Jenkins issue (JENKINS-5931). Maybe having an > access control based on IRC operators and voices? > yeah, using voices would work, but then that would mean that it is only a read only channel for most people, which imo would be a bad move. I mean it would be really nice, if people could drop by to our qa related irc room and start talking about that pesky build failure. another solution would be to set up a custom irc bot, independently from jenkins, which could fetch the build results through the mailing list or rss and send it to the channel. of course extending the jenkins irc bot is also a possibility, the easiest way would be having a configuration option for disabling the whole control stuff, as we don't really need the interactivity there, you can use the web interface for that. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --000e0cd539b68923ab04b0d9e4f4--