Using [`ringctl`] operations in pipelines
This document explains how to perform ringctl operations using pipelines, which serves as an alternative to running ringctl without having to set up the CLI locally. This can be particularly useful for anyone onboarding on to the Delivery Team or team members that do not have the latest version of the CLI set up locally.
Where to execute the pipelines
Section titled “Where to execute the pipelines”The pipelines are to be executed from the Tissue repository on ops.gitlab.net. Check out the pipelines creation interface to get started right away.
Patching
Section titled “Patching”Learn more about patching here.
Available operations
Section titled “Available operations”Most basic operations available in the ringctl CLI can be executed from the pipeline. Please note that this pipeline exclusively uses inputs and that variables can’t be used to execute any ringctl operation.
| Operation | Required arguments | Other arguments |
|---|---|---|
get | patch_id | amp_environment |
ls | N/A | amp_environment |
retry | patch_id | amp_environment, dry_run |
invert | patch_id | amp_environment, priority, dry_run |
delete | patch_id | amp_environment, dry_run |
Ways to execute those pipelines
Section titled “Ways to execute those pipelines”It is possible to declare a pipeline using the pipelines creation interface. Automation can be used as well and inputs can be passed in via the Trigger pipelines API. Here’s a small example:
curl --request POST \ --form token=TOKEN \ --form ref=main \ --form "inputs[ringctl_operation]=ls" \ "https://ops.gitlab.net/api/v4/projects/793/trigger/pipeline"This will execute ringctl patch ls -e cellsdev on the Tissue repository.