Run Ruby 3 in merge requests and default branch
What does this MR do and why?
-
Introduce label and mechanism for ~"pipeline:run-in-ruby2"
so that we can still run Ruby 2 pipeline in merge requests-
Swap CI job verify-ruby-2.7
toverify-ruby-3.0
so we keep the same logic that we always run Ruby 3 before merging into the default branch. -
Label pipeline:run-in-ruby2 created: https://gitlab.com/gitlab-org/gitlab/-/labels/28547941/edit
-
-
Rename ruby3
branch toruby2
branch, and change corresponding pipeline schedules https://gitlab.com/gitlab-org/gitlab/-/pipeline_schedules- Nightly ruby3
- Run ruby3 pipeline every odd hour 5 minutes after sync
- Sync ruby3 branch every odd hour
-
Merge !108110 (merged) -
Rename ruby3-sync
toruby2-sync
-
-
Rename CI/CD variable RUBY3_SYNC_TOKEN
toRUBY2_SYNC_TOKEN
. -
Update protected branches at https://gitlab.com/gitlab-org/gitlab/-/settings/repository -
Update documentation at: doc/development/pipelines/index.md
Current versions testing
Ruby 3.0 jobs
-
Update workflow in .gitlab-ci.yml
to swap the mentioned ones to Ruby 3
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #386172 (closed)
Edited by Lin Jen-Shin