Add CI job for force creating new coordinator pipeline
What does this MR do and why?
Describe in detail what your merge request does and why.
Content
- Add CI job for force creating a new coordinator pipeline
A new coordinator pipeline is usually created only if there are changes to Omnibus or CNG or their components. This change will allow us to trigger a coordinator pipeline even when there are no changes.
This is useful when a new Omnibus/CNG package needs to be created and deployed without pulling in new changes from master. I plan to use this to create Ruby 3.1 packages without pulling in new changes. To create Ruby 3.1 packages, a project variable needs to be set in the Omnibus and CNG projects.
After this is merged, I'll create an inactive scheduled pipeline in https://ops.gitlab.net/gitlab-org/release/tools/-/pipelines.
gitlab-com/gl-infra/delivery#19713 (closed) and gitlab-com/gl-infra/delivery#19807 (closed)
Author Check-list
-
Has documentation been updated?