Skip to content

Notify slack when stable branch failure occurs

Steve Abrams requested to merge delivery2775-notify-broken-stable-branches into master

What does this MR do and why?

Updates CI to enable pipeline failure slack notifications on stable branches.

The delivery group is expanding the maintenance policy to include the three most recent versions. We are doing this by allowing engineers to merge directly into the stable branches for those releases. Since we are allowing direct merges, we need to be notified when we have a failing pipeline due to merges on these branches. This change will add slack notifications for failures to the #releases channel. There are other safety measures in place to prevent MRs from being merged on branches beyond the last 3 releases, so we can safely target all stable branches and expect only the most recent ones will ever receive activity resulting in failures.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to gitlab-com/gl-infra/delivery#2775 (closed)

Edited by Steve Abrams

Merge request reports