Repository navigation
Add tooling to send email to ci_failure email list on ci failure - #351
Conversation
Updates unwatched CI processes to provide feedback on failure.
pamoroso
left a comment
There was a problem hiding this comment.
I have no idea how to test this but it looks useful and reasonable.
|
testing the code to respond to a failure of workflow is likely to risk a stack overflow or infinite loop. |
|
Who will send the failure emails. That is, what address? I ask because the |
@stumbo just told me that the email is sent from an @interlisp.org bot address, so no need to change anything. |
|
Staging preview for this pull request is available at https://interlisp.github.io/Interlisp.staging/pr-351/ |
|
Perfect - the build failed and sent the expected notice on the initial PR because the issue with Zotero was still broken. Once PR 350 was merged into main and main was merged into this PR, fixing the Zotero issue, it completed deployed the staging site and did not send a failure note. We tested the two conditions we're interested in - generating emails on failures and not skipping the email step when the build works correctly. |
Updates unwatched CI processes to provide feedback on failure.
On failure an email is sent to the interlisp.org group
ci_failures. An example message with the current build failure: