cicd infrastructure ai_generated true

This job is stuck because the project doesn't have any runners online assigned to it

ID: cicd/gitlab-runner-stuck

Also available as: JSON · Markdown
84%Fix Rate
86%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
any active — — —

Root Cause

GitLab CI job is stuck in pending state because no registered runner matches the job's tags, the runner is offline, or shared runners are disabled for the project.

generic

Workarounds

  1. 90% success Verify runner registration and ensure tags match the job requirements 
    Go to Settings > CI/CD > Runners and check runner status. Ensure the runner's tags match the tags specified in .gitlab-ci.yml. Re-register the runner if needed with 'gitlab-runner register'
  2. 88% success Enable shared runners or register a new project-specific runner 
    Go to Settings > CI/CD > Runners > Enable shared runners (if available on your GitLab instance). Or register a new runner: 'gitlab-runner register --url https://gitlab.com --token YOUR_TOKEN'

Dead Ends

Common approaches that don't work:

  1. Remove all tags from the job to run on any runner 50% fail

    Untagged jobs may run on inappropriate runners (wrong architecture, missing tools, insufficient resources), causing build failures

  2. Restart the GitLab web application expecting it to fix runner connectivity 85% fail

    The GitLab application server and the runner are separate processes; restarting GitLab does not affect runner registration or connectivity

Error Chain

Leads to:
Preceded by:
Frequently confused with: