Check your GitLab CI rules: before they surprise you
Drop in a .gitlab-ci.yml and see, job by job, which rules: if: can
never match, which mix operators without parentheses, which ones rely on a variable merely being set,
and which variable values actually make each rule fire — all worked out in this browser tab.
1. Your pipeline file
.gitlab-ci.yml here, or click to browse.
2. Included files (optional)
If your pipeline uses include: local:, add those files too — drop them loose and
they are matched to the include by file name, or choose your repository folder to keep every path exact
(only .yml/.yaml files are read). include: remote:,
project:, template: and component: are not fetched.
3. Variable values to try
For every rule, the checker tries each combination of these values for the variables that rule
uses, and lists the combinations that make it match. The defaults cover the common predefined variables —
add your own, or drop in a variables.yaml of the same shape.
variables.yaml here, or click to browse.4. Jobs to check (optional)
5. Simplify a rule (optional)
Results Sample data
Summary
While loading your files
Add a pipeline file, or load the sample, to see results here.
Plain-language summary
Pipelines doing things nobody expected? ReleaseTEAM untangles GitLab CI/CD for teams of every size.
Talk to ReleaseTEAM about your pipelines