`oore pipeline validate`
Validate repository pipeline YAML with the same schema used by the runner.
oore pipeline validate [PATH]PATH defaults to .oore.yaml. The command reads the selected file and
validates it with the runner’s repository pipeline parser. It accepts
version: 1 and version: 2 files, and for version 2 checks every workflow,
including vars, step and target references.
oore pipeline validate
oore pipeline validate config/mobile.oore.yamlA valid file prints:
.oore.yaml is validInvalid YAML, an unknown field, an unsupported schema version, an empty platform list, a duplicate environment key, an invalid artifact pattern, or an undefined or cyclic reference returns a non-zero exit and a specific validation message. Shape errors include the line and column.
For a version 2 file, the command prints note: lines on standard error for
settings that change how the pipeline behaves, such as on replacing the
trigger settings, publish replacing the Publish settings, or a workflow that
publishes to Google Play without an Android build that makes an App Bundle. It
still exits successfully.
The command validates only the selected file. It does not contact the backend, create a pipeline, or verify whether every command-line tool used by the pipeline is installed.
See .oore.yaml and
.oore.yaml version 2 for the schemas, and
oore pipeline plan to print the steps a
file runs.