Re: CI for 5.4

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 local >> 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.qaon 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] > > :( > > -- > Ferenc Kovács > @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/ -- Ferenc Kovács @Tyr43l - http://tyrael.hu