Slack notification for background migration failures
Problem to solve
To improve visibility of background migration failures
Target audience
GitLab developers
Further details
For developers writing background migrations, it has been a little difficult to be informed about failures after it is deployed. It would be nice if failure backtrace and failure count can be delivered to Slack and pin the relevant MR author.
Proposal
A way to alert on Slack that a particular type of background migration fails, and if possible ping the MR author.
Documentation
n/a
What does success look like, and how can we measure that?
MR author being able to detect failure, but at the same time not flooded by it if too many jobs have failed.