To follow up on the question of coalescing emails, it looks like it should be possible to write a daily job which gathers up all of the job statuses and sends an email. This forum thread suggests a way in which it could be written using Groovy: http://jenkins-ci.361315.n4.nabble.com/generating-a-daily-weekly-report-on-job-status-by-mail-td3766477.html -Austin On Apr 1, 2014, at 3:49 PM, Austin Hendrix wrote: > 1) you’re a maintainer, so you’re automatically subscribed. There isn’t any more granularity to the email settings than that. > 2) There aren’t any settings for this that I’m aware of, but there may be an alternate jenkins notification plugin that can do this. It’s probably worth looking into. > 3) yeah… I really can’t help you here > > Not a real solution, but I filter the emails that I get from jenkins into a separate tag/folder in my email client, so that I can put off looking at them until later. > > -Austin > > On Apr 1, 2014, at 3:45 PM, David Lu!! wrote: > >> So I'd like to start a hopefully constructive discussion of the build >> farm's email practices. I've attached a picture of the onslaught my >> inbox just received. I'm fairly certain none of the builds failing is >> my fault. But it does lead me to some questions. >> >> 1) Are there settings for email that I haven't set to reduce the >> number of emails I get? Or am I automatically subscribed because I'm a >> maintainer? >> 2) Is there a way to condense the emails? If I got a single email >> telling me which packages I maintain failed to build, but this seems a >> bit much. >> 3) I've whined about this before, but is there some way we can make >> the error messages more legible? I'm sure for people familiar with the >> build farm, the errors may make sense, but as a maintainer, I have no >> idea what I'm supposed to do. If the answer is nothing, why am I >> getting email? >> >> I realize accomplishing some of these tasks will likely involve >> substantial amounts of work, but I feel it merits discussion >> nonetheless. >> >> -David >> _______________________________________________ >> ros-release mailing list >> ros-release@code.ros.org >> http://lists.ros.org/mailman/listinfo/ros-release > > _______________________________________________ > ros-release mailing list > ros-release@code.ros.org > http://lists.ros.org/mailman/listinfo/ros-release