Skip to content
BENIBIX Learn

GitLab CI/CD

Development☁️ DevOps & CloudCI/CD

Also known as GitLab CI, .gitlab-ci.yml, GitLab Pipelines

The CI/CD tool built into GitLab. You set it up in a .gitlab-ci.yml file.

Think of it like

Think of it like a to-do list kept in the project folder. GitLab reads it and does each task when code changes.

Example

Lucy adds a .gitlab-ci.yml with a test job. Every merge request now shows a green tick or a red cross.

Why it matters

Code, reviews and pipelines live in one place, so teams need one tool, not three.

Definition

GitLab CI/CD is the pipeline tool built into GitLab. You describe the pipeline in a file called .gitlab-ci.yml, in the root of the project. The file lists stages and the jobs in each. Runners pick up the jobs and run them. Results show next to each merge request.

Example code

yaml
test:
  image: node:22
  script:
    - npm ci
    - npm test
One job that installs packages and runs the tests on each push.
GitLab reads the pipeline from .gitlab-ci.yml.

Common mistake

Saving the file with the wrong name. GitLab looks for .gitlab-ci.yml, unless you pick a new name in the settings.

Key takeaways

  1. 1
    One file. .gitlab-ci.yml in the project root.
  2. 2
    Stages and jobs. Jobs run inside stages.
  3. 3
    Runners run it. Hosted or your own.