[ci] Skip slack alerts if retried tasks succeeded #15869
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently for pipelines that have steps with auto retries, if there is a failure of a step, even if the subsequent retry succeeds, we received Slack alerts. This commits uses new functionality available in the Buildkite PR Bot to avoid Slack notifications in those cases and changes the settings for all pipelines where we have, or expect to have, retries.
alexsapran
approved these changes
Jan 29, 2024
|
0.0% Duplication on New Code
💚 Build Succeeded
cc @dliappis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release notes
[rn:skip]
What does this PR do?
Currently for pipelines that have steps with auto retries, if there is a failure of a step, even if the subsequent retry succeeds, we receive Slack alerts.
This commits uses new functionality1 available in the Buildkite PR Bot to avoid Slack notifications in those cases and changes the settings for all pipelines where we have, or expect to have, retries.
Why is it important/What is the impact to the user?
Reduce alert noise for non-actionable events in the Slack channel.
How to test this PR locally
Can't be tested, needs to be merged for the change to get picked up by terrazzo.
Footnotes
https://github.com/elastic/kibana-buildkite-build-bot/commit/95102e37dd14e95cf8c5eb32a4027d6b14f3fb73 ↩