Create metric for patch release information + status
Context
In &1245 (closed), we created the metric delivery_release_monthly_status
to capture and display information about the monthly release on the release information dashboard.
With this issue, we aim to create a very similar metric delivery_release_patch_status
for the patch releases.
As captured on this list of patch release information to display on Grafana, let's create that metric with the following labels:
-
versions
: Upcoming patch release versions, leveraging gitlab-releases gems'next_versions
function in GitlabReleasesClient in release-tools -
release_date
: Upcoming patch release date, similarly to above, leveragingnext_patch_release_date
function
The value of the metric dictates the current status:
- 1 = open: Similar to the "Open" status for the monthly release status (green), this status signifies that any security-target labelled security issues would be included in the next patch release.
- Created during the "security_release_finalize:start" job of the previous patch release for the next versions. (internal example)
- 2 = warning: Similar to the "Announced" status for the monthly release status (yellow), this status signals that the merging date for patch release is getting closer.
- Metric value updated 4 business days (Thursday) before the next patch release date (Wednesday).
- Idea for implementation: a pipeline schedule that runs every Thursday UTC 00:00 using cron job scheduler, checks if it's the Thursday before the next patch release date, if so, updates the metric
- Metric value updated 4 business days (Thursday) before the next patch release date (Wednesday).
- 3 = closed: Similar to the "Tagged RC" status for the monthly release status (red), this status signals that security MRs have been merged, and security-target security issues may no longer be added to the upcoming patch release.
- Metric value updated during default security MR merging pipeline. (
/chatops run release merge --security --default-branch
) (internal example)
- Metric value updated during default security MR merging pipeline. (
Exit Criteria
-
delivery_release_monthly_status
is created with theopen
status during the finalize job of the previous patch release for the next versions -
(waiting until the next patch release cycle to validate) delivery_release_monthly_status
is updated with thewarning
status 4 business days before the next patch release date -
(waiting until the next patch release cycle to validate) delivery_release_monthly_status
is updated with theclosed
status after the default security MRs are merged
Edited by Jenny Kim