When https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Releng/job/push-container-to-quay/configure and https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Releng/job/push-latest-containers-to-quay/configure fail, they don't send emails.

We should parse the console log for specific error(s) and warning(s), then send emails accordingly.

This could be done using Editable Email Notification and the Trigger = Script - After Build with custom groovy logic.

Or, we could reuse what we have already in the Theia Jenkinsfile [1],[2] or the console parser [3],[4].

[1] https://github.com/redhat-developer/codeready-workspaces-theia/blob/master/Jenkinsfile
[2] https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Pipelines/job/crw-theia_master/

[3] https://github.com/redhat-developer/codeready-workspaces-jiralint/blob/master/util/console-log-parser.txt
[4] https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/get-sources-rhpkg-container-build/configure

DoD:

• push-container-to-quay and push-latest-containers-to-quay sends email for warnings/failures to whoever broke the build + owners (nboldt@ mkuznets@)
• obvious call to action (if using log parser, call to action is "check the job for the parsed log, find the problem, fix it")