The attached files show the various status emails which occur:
1) Successful build, unittest, doxygen generation, and comparison
2) Failure due to fatal 'scons' build result
3) Failure due to fatal unittest result
4) Failure due to random error - system blocked, missing resource, failed doxydoc generation, failed end-to-end testing, etc.
The email recipients are chosen based on how the buildbot job was triggered. If a user personally triggered the build using the DM_stack "ForceBuild" form, the email (success and failure) will only be sent to the email address provided by the user.
If the DM_stack build was triggered by the gitolite-repo-change trigger, then the failure output will be sent to the listserv: [lsst-dm-dev].
During development, the consensus formed that all status reports from the repo-change trigger should be sent to a listserv address. So redirecting based on the type of error was not included in this version. It is trivial to re-institute if the consensus swings back.
Future work related to triggers and email notification:
DM-703 adds HipChat notification on every build (success or failure).
DM-955 adds stash-repo-change trigger to handle stash repositories.
DM-956 adds to the status email the branches used during a build. Incorporating non-master branches is only possible during user-triggered ForceBuild.