differentiate between build/test errors vs configuration errrors

[tfoote]

This should prevent users from getting emails about something like github being down.

[tfoote]

The challenge with this is that we will need to find a way for jenkins to catch these premature failures and abort.

[dirk-thomas]

For each section we should print a unique line stating in which state the script is in. Then a groovy script can look for those known markers and decide on notification.

[trainman419]

It looks like the Email-ext jenkins plugin has a pre-send script feature which allows it to cancel email notifications: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin

Perhaps this could be used to disable email notifications for configuration errors and hash sum mismatches.

[dirk-thomas]

The difficult question is when to flip that switch. If it is only switched w.g. when "hash sum mismatch" is in the output then the maintainer still gets an email for the next job when it became stable again.