[
https://issues.apache.org/jira/browse/FLINK-34326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831255#comment-17831255
]
Ryan Skraba commented on FLINK-34326:
-------------------------------------
It looks like subscribing to failed workflows is [currently
unsupported|https://github.com/integrations/slack/issues/1563] in the GitHub
integration for Slack (already installed on the flink slack instance). If it
were, we could simply subscribe to the relevant event in the #builds channel :/
One alternative is to use one of the github slack notification actions (noting
ravsamhq/notify-slack-action as an alternative in the issue above). I can take
a look at what INFRA prefers as an action.
Another alternative would be too subscribe to *all* of the workflow completed
events from GitHub, including successful and canceled events. There were about
50 runs over the last week, with only 14 of them were failures to be
investigated. This isn't perfect but it's also not unreasonable!
> Add Slack integration
> ---------------------
>
> Key: FLINK-34326
> URL: https://issues.apache.org/jira/browse/FLINK-34326
> Project: Flink
> Issue Type: Sub-task
> Reporter: Matthias Pohl
> Priority: Major
>
> There are Slack actions (e.g.
> [actions/slack-github-actions-slack-integration|https://github.com/marketplace/actions/slack-github-actions-slack-integration])
> available. They usually require some secrets to be specified. Hence, it
> might be worth it to resolve FLINK-34322 beforehand to verify that secrets
> work properly with the workflows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
