Report card

Do AI agents pick GitLab CI/CD?

How often agents choose GitLab CI/CD when a developer needs ci/cd — measured across Claude, GPT, Gemini.

GitLab CI/CD

#3 of 6 ci cd
0%Pick Rate
95% CI 0%3%

When developers ask an AI agent for ci cd, GitLab CI/CD is picked 0% of the time — ranking #3 of 6 measured across Claude, GPT, Gemini.

Picked 0% Named, not picked 76% Never surfaced 24%

Beaten by GitHub Actions (28%), Buildkite (5%).

Awareness

14 docs in FineWeb (10BT sample) · 1.6K URLs in Common Crawl

Present in the raw crawl and the filtered corpus models train on — solid corpus footprint.

AdoptionDid the pick convert to installs? Public Adoption = npm downloads of your packages. The proof half of the funnel.

5.8M installs / month ▼ 1% MoM

Installs are roughly flat month over month.

Get the full report

The per-model and per-surface breakdown for GitLab CI/CD — where it wins, where it loses, and to whom — plus an alert when the Pick Rate moves.

About GitLab CI/CD

GitLab's built-in continuous integration and delivery system for automating build, test, and deployment pipelines.

GitLab CI/CD is the pipeline automation layer built directly into GitLab, allowing teams to define build, test, security scan, and deployment workflows in a `.gitlab-ci.yml` file stored alongside their code. It supports runners on Linux, Windows, and macOS, and works with self-hosted GitLab instances as well as GitLab.com. It is aimed at development teams that want integrated source control and pipeline management without connecting a separate CI service.

Where to start

Add a `.gitlab-ci.yml` file to the root of your GitLab repository to define your pipeline stages and jobs. GitLab's documentation covers the configuration syntax, available runner executors, and how to register your own runners.

Install

Links and summary verified from public sources.

The rest of the CI/CD ranking

← Full CI/CD leaderboard · How this is measured