Keep track of an on-going deployment
As part of #1241 (closed), we're sending notifications to Slack when a deployment to production is in progress:
Slack notifications example |
---|
The overview should link to the job URL, so instead of having a cryptic message, we should have Production deployment reached [gprd-git 8](link to gprd-git job) . This bug is being tracked on #1241 (comment 447270078)
|
These notifications are sent when intermediate points are reached on the deployment pipeline, specifically they are sent at the end of each deploy_gitlab
ansible batch using post_tasks
(see https://ops.gitlab.net/gitlab-com/gl-infra/deploy-tooling/-/merge_requests/314), which means that for a single job (e.g gprd-migrations
) multiple notifications will be sent to Slack.
So far, these notifications have been very spammy, and I'm not sure if there's any value in sending a notification if there are no active incidents.
Proposal
To make the most out of these notifications, I propose to:
- Send a Slack notification to
#announcements
if there's a deployment in progress and if there's an active incident (or if checks are failing)
As a follow up, we could wrap these notifications in a single Slack thread.
To do
-
Modify notifications to only be sent if a deployment is in progress and if checks are failing - gitlab-org/release-tools!1281 (merged) -
Modify notifications to be sent to #announcements
channel - gitlab-org/release-tools!1291 (merged)