Automation to create an issue into the Dedicated Tracker when Critical Security Release issue is created
Context
Based on #19538 proposal, we identified some improvements in the current process that could eliminate some manual action, and improve automation and communication when Critical Security Releases are created.
Problem
Currently when a new critical security release issue is created:
- Release Managers are notified by SIRT/AppSec of a new Critical Security issue.
- Release Managers create, via Chatops
/chatops run release prepare --security --critical
a new Critical Security Release Issue in https://gitlab.com/gitlab-org/release/tasks/ tracker for Release Managers. - Release Managers manually notify Dedicated of the presence of a new Critical Security Release.
The time between 2 and 3 can vary and the Dedicated team can incur timing problems due to tight schedules on the tenant maintenance window.
Timely notify Dedicated of a new release will set Dedicated upgrades for success.
Ideal Solution
Ideally we should automate 2. and 3. of the steps above:
- Release Managers are notified by SIRT/AppSec of a new Critical Security issue.
- Release Managers create, via Chatops
/chatops run release prepare --security --critical
a new Critical Security Release Issue in https://gitlab.com/gitlab-org/release/tasks/ tracker for Release Managers. This automatically will create an issue on the Dedicated Tracker (using a Dedicated provided template).
In this way we eliminate the human factor and rely on automation.
Edited by Michele Bursi