dcloud ci runner-groups create

Create a runner group

IAM ci:ManageRunnersChanges stateAsks before it deletes (-y skips)

A run reaches a runner of the group only when its repository, its ref and its event are all allowed. A merge queue build is judged by the branch it lands on.

Synopsis

dcloud ci runner-groups create --name name [flags]

Flags

  • --nameRequired

    string

    Name of the group, 1 to 100 characters: letters, digits, spaces, . _ -, starting with a letter or digit; unique in the organization (409)

    Constraints: 1-100 chars

  • --repository-idsOptional

    array of string

    Repositories the group serves, up to 500, each a repository of this organization (404 otherwise); null or omitted: every repository

    Constraints: uuid

    May be null.

  • --refsOptional

    array of string

    Ref globs it serves (`main`, `release/*`, `refs/tags/v*`), up to 50 of up to 200 characters (letters, digits, * . _ / -); omitted or empty: any ref

    Constraints: 1-200 chars

  • --protected-refs-onlyOptional

    boolean (--protected-refs-only / --no-protected-refs-only)

    Only branches covered by a branch protection rule; for runners that hold deploy credentials. Off when omitted

  • --allow-pull-requestsOptional

    boolean (--allow-pull-requests / --no-allow-pull-requests)

    Whether pull-request runs reach it; on when omitted

Example

dcloud ci runner-groups create --name example

Generated from the API description, the same one the API checks requests against and the CLI is built from.