Proposal: Add weekly handling of deployment blockers into RM duties
Problem
During RM rotations there are several occasions when a problem will stop auto_deploy, e.g., an incident, a qa failure, etc. The RM is usually opening an incident or an issue on the release tracker and closing it when the problem is solved. These issues should have a release-blocker label associated with a label related to the time the issue impacted the deployment to a specific environment, e.g., Deploys-blocked-gprd3hr Deploys-blocked-gstg3hr
Currently, the activity that takes a good amount of time, recurring every week, is to go through all the incidents and release issues and verify that are properly labeled. Summarize them in a spreadsheet and update the &659 (closed) epic.
This task is currently highly manual and executed by the EM of ~"team::Orchestration" or ~"team::System".
Proposal
-
Create a report listing the blockers from the previous week and assign it to release managers gitlab-org/release-tools!1983 (merged) -
Ensure the report has specific instructions to update the spreadsheet and the epic gitlab-org/release-tools!1985 (merged)
Follow-ups
- Consider change requests in the report - #2610
- Automatically fill out the information on &659 (closed) - #2611