<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">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.<div><br></div><div>This forum thread suggests a way in which it could be written using Groovy: <a href="http://jenkins-ci.361315.n4.nabble.com/generating-a-daily-weekly-report-on-job-status-by-mail-td3766477.html">http://jenkins-ci.361315.n4.nabble.com/generating-a-daily-weekly-report-on-job-status-by-mail-td3766477.html</a></div><div><br></div><div>-Austin</div><div><br></div><div><div>On Apr 1, 2014, at 3:49 PM, Austin Hendrix <<a href="mailto:legotown@aol.com">legotown@aol.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">1) you’re a maintainer, so you’re automatically subscribed. There isn’t any more granularity to the email settings than that.<br>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.<br>3) yeah… I really can’t help you here<br><br>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.<br><br>-Austin<br><br>On Apr 1, 2014, at 3:45 PM, David Lu!! <<a href="mailto:davidlu@wustl.edu">davidlu@wustl.edu</a>> wrote:<br><br><blockquote type="cite">So I'd like to start a hopefully constructive discussion of the build<br>farm's email practices. I've attached a picture of the onslaught my<br>inbox just received. I'm fairly certain none of the builds failing is<br>my fault. But it does lead me to some questions.<br><br>1) Are there settings for email that I haven't set to reduce the<br>number of emails I get? Or am I automatically subscribed because I'm a<br>maintainer?<br>2) Is there a way to condense the emails? If I got a single email<br>telling me which packages I maintain failed to build, but this seems a<br>bit much.<br>3) I've whined about this before, but is there some way we can make<br>the error messages more legible? I'm sure for people familiar with the<br>build farm, the errors may make sense, but as a maintainer, I have no<br>idea what I'm supposed to do. If the answer is nothing, why am I<br>getting email?<br><br>I realize accomplishing some of these tasks will likely involve<br>substantial amounts of work, but I feel it merits discussion<br>nonetheless.<br><br>-David<br><Screenshot from 2014-04-01 17:30:36.png>_______________________________________________<br>ros-release mailing list<br><a href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a><br>http://lists.ros.org/mailman/listinfo/ros-release<br></blockquote><br>_______________________________________________<br>ros-release mailing list<br><a href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a><br>http://lists.ros.org/mailman/listinfo/ros-release<br></blockquote></div><br></body></html>