Ensure slack notifications for stable branch failures are only sent for active stable branches.
When a stable branch fails, a Slack notification is sent to the #releases
channel with the purpose of addressing the failure. When implementing #2775 (closed), the blocker that prevents merging bug fixes into stable branches was considered, but this one will be removed on #2822 (closed) because it is not compatible with the long-term goals of the new maintenance policy.
The purpose of this issue is to guarantee slack notifications are only sent for stable branches inside the maintenance policy.
Implementation details
As of today, it is not possible to have logic in workflow:rules
to dynamically determine the last three versions, until that is implemented, we would need at least two merge requests:
- One to update the CI configuration on master with the active stable branches
- Another one is for updating the CI configuration of the version that will be outside of the policy, e.g if the 15.9 stable branch was being created, we will need to update the CI configuration for 15.6
These merge requests might need to be backported to stable branches. Details on #2823 (comment 1280178449)
Previous version
- Add a CI rule on the GitLab project to trigger that notification only for versions inside the policy. Note that it is not yet possible to have logic in
workflow:rules
to dynamically determine the last three versions, so it'd have to be hardcoded (example) - Add a step on the monthly release template to update the CI rule.