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? On Thu, Nov 3, 2011 at 5:33 PM, Stefan Marr <p...@stefan-marr.de> wrote: > Hi: > > On 03 Nov 2011, at 20:15, Ferenc Kovacs wrote: > > > 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. > > If I get a personal notification via mail, if I break something, that kind > of guarantees my attention. Using IRC is to distracting, so that is not an > option for me. Sorry. > > If I am the only one who would use it, then don't bother. But if I can > simply opt-in for it somewhere, that would be great. > > Thanks to people like Antony, obviously stupid bugs get caught pretty fast. > > Thanks > Stefan > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > -- Klaus Silveira (011) 8564-2492 www.klaussilveira.com
