Pipeline Inputs

For pipelines using spec: inputs:, pass values via CLI flags or a YAML file.

Usage#

glci run --input force_build=true --input runner_version=17.6.0
glci run --inputs-file inputs.yml
glci run --inputs-file defaults.yml --input force_build=true  # CLI overrides file
glci show --input force_build=true                            # works with show too

Input types#

Type	Accepted values	Normalization
`string`	Any value	None
`boolean`	`true`, `false`, `yes`, `no`, `1`, `0`	Normalized to `true`/`false`
`number`	Any valid number	None
`array`	Any value	Formatted as YAML flow sequence

Inputs file format#

# inputs.yml
force_build: true
runner_version: "17.6.0"
environment: staging

Validation#

glci validates inputs before starting the pipeline:

Required inputs: Inputs without a default must be provided. Error messages include the input’s description if available.
Type checking: Boolean inputs reject non-boolean values; number inputs reject non-numeric values.
Options: When options: is declared, the provided value must match one of the listed options.

Interactive TUI#

The TUI (glci with no subcommand) shows an input form with descriptions and defaults pre-filled. Required inputs are highlighted and validated before submission.

Edit on GitLab Report issue