GitLab CI YAML Validator
Check a supplied .gitlab-ci.yml for local stages, script types, needs, extends and trigger rules. Save diagnostics with source locations.
Diagnose a GitLab Pipeline from Saved YAML
Checks the supplied YAML in this browser. Commands and expressions stay as text.
GitLab CI YAML Validator: how to use it
- Paste the GitLab CI file, open a local copy or load the two-stage example.
- Select Validate GitLab CI. Read errors and warnings beside the affected path and source position.
- Update the pipeline and download the revised JSON diagnostic report.
Limits and notes
196,608 input characters, 48 YAML levels and 512 jobs. Checks use the supplied document and supported platform rules. Internal aliases and local extends are checked. Includes, cross-project dependencies and GitLab reference expansion require the full project.
How your privacy works →GitLab CI YAML Validator: common questions
Can the check see hidden templates?
It uses local mappings such as .base for extends and excludes hidden templates from the runnable job count.
What happens to fields imported with include?
The checker flags deferred context and warns where missing names could be supplied by an include. GitLab CI Lint can resolve the included configuration where it has access.
Why does a script line with a colon raise a type error?
YAML can read a colon followed by a space as a key-value separator. Quote the whole command or use a block scalar to keep it a string.