On Thu, Aug 9, 2012 at 7:56 PM, Ewan Mellor <ewan.mel...@eu.citrix.com> wrote: > Hi all, > > We've got various Jenkins jobs now, and these are going to be useful for > telling us when the build breaks or when tests fail. I was planning to turn > the email notification on as soon as these jobs are stable and passing. > > What do people want me to do with the email notification for these jobs? I > could > * send them to this list (with some prefix so that you can filter them); > * get a separate list created, which interested people can subscribe to; > * dump them in /dev/null so that you never hear of them again, and rely on > people checking up on the job health periodically; > * something else? >
I was thinking about this today from the docs build pov and then looking at all of the other build jobs. Currently junit would be so noisy right now, and this already a high-traffic list, so I'd personally only turn on notifications for builds that have stabilized. Cascading failed build notifications don't serve a useful purpose IMO, and even then I'd make it a separate list. --David
