Send a Slack message when pipelines on stable branches failed.
Delivery is working to extend the GitLab maintenance policy to support bug fixes to the two previous monthly releases in addition to the current stable release. Part of this work will open up the stable branches to allow developers to merge bug fixes directly into the stable branch rather than rely on the pick labels.
Just like the master branch, stable branches could be subjected to failures and when these occur they need to be surfaced so they can be fixed in a timely manner.
Proposal: Send a slack message when a failure on a stable branch occurs
Similar to broken-master failures, a message should be posted in Slack when a failure on a stable branch occurs:
- The message should be posted in the
#releases
Slack channel - It should include the name of the branch, the commit that originated the failure and the job that failed.
- Messages should only be posted for branches inside the policy, for example, currently we should monitor 15-7-stable-ee, 15-6-stable-ee and 15-5-stable-ee.
- Since we have Danger set to fail on any MRs targeting versions outside the maintenance policy, it is unlikely MRs will be merged into older branches, so we can allow messages for all stable branches and not worry about adding specific logic to the CI rules.