Add a new ruby3 branch synchronization pipeline schedule
What does this MR do and why?
Add a new ruby3 branch synchronization pipeline schedule.
- A new project token is created and called
ruby3-sync
: https://gitlab.com/project_278964_bot10- It has
read_registry
andwrite_repository
permission as adeveloper
- It will expire in
2023-10-01
(I expect we remove this before it's expired)
- It has
- A new CI/CD variable is created and called
RUBY3_SYNC_TOKEN
- It's
protected
andmasked
-
After merged: Re-enable protected
because it's disabled for testing in this merge request
-
- The scope is set to
ruby3-sync
- The value is the project token for
ruby3-sync
- It's
- A new branch
ruby3-sync
from an orphan commit isprotected
, andmaintainers
can merge,no one
can push - A new branch
ruby3
frommaster
isprotected
, andmaintainers
can merge,ruby3-sync
can push - A new pipeline schedule "Sync ruby3 branch every odd hour"
-
After merged: Enable the schedule https://gitlab.com/gitlab-org/gitlab/-/pipeline_schedules
-
Examples:
- Sync: https://gitlab.com/gitlab-org/gitlab/-/jobs/2967995146
- A pipeline is triggered: 8399d974
Setting screenshots
ruby3-sync
Project token (Note: The screenshot was outdated, and it should have permission for read_registry
and write_repository
instead)
RUBY3_SYNC_TOKEN
CI/CD variable
ruby3-sync
and ruby3
Protected branches
Pipeline schedule
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Edited by Lin Jen-Shin