Send Slack notification if test-install.yml fails #6897
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the Slack notification step to the
test-install.yml
workflow that runs automatically on the main branch, but until now any failures were not reported, so we for example missed the problem with the new click version (#6885).To prevent duplication I've created a new
slack-notification
action, and use it in bothnightly.yml
andtest-install.yml
workflows.Lastly, I decided to skip the notifications on runs triggered from pull requests (regardless whether they come from fork or origin) since in that case the failure is obvious in the GitHub UI so no need to send message to Slack.
This PR from is intentionally from the origin repo so that I could test that the notifications actually work, and indeed they are, see messages in the
#aiida-core-dev
Slack channel from May 26. To see that the notifications are properly skipped, see #6896.