Automate tagging of monthly release
What does this MR do and why?
Describe in detail what your merge request does and why.
Content
- Automate tagging of monthly release
Instead using ChatOps command, tag the monthly release using a release pipeline job, to improve visibility and automaticity.
- Add rake tasks to notify and perform tagging of monthly release.
- Add CI jobs to notify and perform monthly tagging:
- After the
monthly_release_tag_day:ensure_stable_branches_green
andmonthly_release_tag_day:mirror_status
jobs completed successfully, notify about the start of tagging - Automatically start the tagging step after the notification
- After the
- Update the monthly issue template for this change.
Testing
Pipeline creation
With |
With |
---|---|
Configuration testing
This was to test the pipeline configuration (the job order). I updated the jobs monthly_release_tag_day:start
, monthly_release_tag_day:ensure_stable_branches_green
and monthly_release_tag_day:mirror_status
to echo the bundle rake tasks and disable the monthly_release_tag_day:check_omnibus_packages_tagging
to just focus on the tagging step.
Step | Screenshot |
---|---|
Initialized as a manual pipeline | |
After |
|
The job |
|
The job |
|
Slack notification after tagging of monthly release |
Related Issue: gitlab-com/gl-infra/delivery#20472 (closed)
Author Check-list
-
Has documentation been updated?