Add CI configuration and initial job for monthly release pipeline
Context
To speed up the monthly release preparation and remove manual work from release managers, we're automating the last steps of the monthly release pipeline. Details on &1076
Proposal
- Create a new pipeline:
monthly-release-day
that can be manually run using a variable$MONTHLY_RELEASE_PIPELINE
set to'release_day'
. This is a similar strategy to the security release pipeline: we are using a specific value for the variable so in the future, we can run other pipelines that can be run with the same variable using different values.
This pipeline should have one single job for now that:
- Notifies the release manager has triggered the final steps for the monthly release via Slack. Similar to:
- This job should be manual.
- Create a
monthly_release_pipeline
feature flag on ops that is disabled by default. This one should control when the monthly release pipeline will be used - When the feature flag is enabled, add the following step on the
22nd: release day
Start the release day preparation by manually running a pipeline with $MONTHLY_RELEASE_PIPELINE set to 'release_day'
Edited by Mayra Cabrera