On Thu, Nov 3, 2011 at 10:22 PM, Felipe Pena <felipe...@gmail.com> wrote:
> 2011/11/3 Ferenc Kovacs <tyr...@gmail.com>: > > On Thu, Nov 3, 2011 at 8:41 PM, Klaus Silveira < > cont...@klaussilveira.com>wrote: > > > >> 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 > an > >> 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. > > > > -- > > Ferenc Kovács > > @Tyr43l - http://tyrael.hu > > > > Nice work with this Jenkins stuff! The system seems pretty useful. > I like the idea to have a mailing list for build result notification, > as well as send mail to the build breaker. Thanks for the feedback. We could set up the email notification any time, we would just have to agree where to send (internals, php-qa, creating a dedicated mailing list?) and when to send (as I added to the RFC, having failing tests can be a problem from the notification POV). We have to find a good middle way, else we will either miss the notifications, or we will be overwhelmed, so people will just ignore it. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
