Improve Runner group release process - Part Two - Automate GitLab Runner Operator and apply incremental improvements
With #29456 (closed) we automated the bulk of GitLab Runner and Chart release.
In this next part we would want to:
- Automate Operator release
- Operator currently is released manually by running the release steps locally and pushing the changes to 3 different GitHub repos.
- This will involve automation in the Operator pipeline and then calling that pipeline with a regular release, just like Chart
- Apply incremental changes - There are opportunities left over from the first iteration to improve upon the overall experience. We could apply these changes when the opportunity arises, otherwise they are fine for the final part 3 of this
-
gitlab stable release
job found in GitLab Runner has to be made a manually ran job that will be executed from therelease pipeline
. This will make sure that the releaser will call all the releases in the correct order resulting in correctly ordered releases in the RELEASES page of the project. - the release pipeline should wait for the stable branch to finish (this is 95% done anyways)
- More to add here
- UBI images - will need to be handled by the release project to ensure Operator releases go smoothly
Edited by Georgi N. Georgiev