GitLab Pipeline Not Running or "yaml invalid"

How to fix it

Try these in order — the most common fix is first.

1. 1. Validate the YAML

   Copy steps
   1. Open Build > Pipeline editor or CI/CD > Editor, which highlights errors.
   2. Or paste the file into CI Lint.
   3. Check for misspelled keywords and jobs missing script or trigger.
   Did this fix it? Yes No

2. 2. Review rules and workflow

   Copy steps
   1. Print $CI_PIPELINE_SOURCE in a test job to see the real value.
   2. Check workflow:rules and each job rules; no matching job means no pipeline.
   3. Do not mix rules with only/except.
   Did this fix it? Yes No

3. 3. Fix merge blocked by "Pipeline must succeed"

   Copy steps
   1. Confirm a pipeline is created for the source branch and passes.
   2. If the project has no CI, turn off "Pipelines must succeed" in Settings > Merge requests.
   3. For "Checking pipeline status" stuck, refresh, close and reopen the MR, or run /rebase.
   Did this fix it? Yes No

4. 4. Split big pipelines

   1. If creation times out, reduce matrix combinations or use parent-child pipelines.
   Did this fix it? Yes No

Symptoms

Push or merge request creates no pipeline, shows a "yaml invalid" badge, or a merge is blocked by "Pipeline must succeed".

Why it happens

• Syntax or indentation error in .gitlab-ci.yml
• rules or workflow:rules leave no jobs
• Mixing rules with only/except
• Pipeline has only .pre/.post jobs
• Too many jobs so pipeline creation times out
• External CI never reported back

This guide also covers

• gitlab pipeline not running
• gitlab yaml invalid
• gitlab pipeline must succeed
• gitlab ci not triggering

Other GitLab errors

• GitLab Permission Denied (publickey) Error
• GitLab Pipeline Stuck on Pending
• GitLab Runner Not Picking Up Jobs
• GitLab "HTTP Basic: Access Denied" on Push or Clone
• GitLab "You Are Not Allowed to Push Code to Protected Branches"
• How to Resolve GitLab Merge Conflicts
• GitLab "No More Compute Minutes" or CI Minutes Quota Exceeded
• Why Is GitLab So Slow?