dcloud ci runner-pools updateChange a pool’s labels, sizes, spare machines or machine reuse
Synopsis
dcloud ci runner-pools update id [flags]Arguments
<id>Requiredstring
Also accepted as
--id. Constraints: uuid
Flags
--labelsOptionalarray of string
Replaces the labels: 1 to 20, each letters, digits, . _ -, up to 50, lower-cased; no macOS label (400); omitted: unchanged
Constraints: /^[a-z0-9][a-z0-9._-]{0,49}$/
--min-sizeOptionalnumber
Machines always on, 0 to 200, not above maxSize (400); omitted: unchanged
Constraints: integer, 0-200
--max-sizeOptionalnumber
Most machines at once, 1 to 200; omitted: unchanged
Constraints: integer, 1-200
--spareOptionalnumber
Idle machines kept above demand, 0 to 50; omitted: unchanged
Constraints: integer, 0-50
--clean-machine-per-jobOptionalboolean (--clean-machine-per-job / --no-clean-machine-per-job)
true: destroy every machine after its job; false: reuse it within its paid hour; omitted: unchanged
--share-trusted-machinesOptionalboolean (--share-trusted-machines / --no-share-trusted-machines)
Let trusted jobs of every repository share machines (pull request jobs never do); omitted: unchanged
--prebuilt-imageOptionalboolean (--prebuilt-image / --no-prebuilt-image)
Boot from the organization's pre-built runner image (true) or stock Ubuntu (false); machines already running keep theirs; omitted: unchanged
--placementOptionalenum
own-hosts-first or cloud-only; machines already running stay where they are; omitted: unchanged
One of:
own-hosts-first,cloud-only
Example
dcloud ci runner-pools update idGenerated from the API description, the same one the API checks requests against and the CLI is built from.