Skip to content

Getting Started

CI/CD process overview

To use GitLab CI/CD:

  1. Ensure you have runners available to run your jobs. If you don’t have a runner, install GitLab Runner and register a runner for your instance, project, or group.
  2. Create a .gitlab-ci.yml file at the root of your repository. This file is where you define your CI/CD jobs.

When you commit the file to your repository, the runner runs your jobs. The job results are displayed in a pipeline.


Pipelines are the top-level component of continuous integration, delivery, and deployment.

Pipelines comprise:

  • Jobs, which define what to do. For example, jobs that compile or test code.
  • Stages, which define when to run the jobs. For example, stages that run tests after stages that compile the code. Jobs are executed by runners. Multiple jobs in the same stage are executed in parallel, if there are enough concurrent runners.

If all jobs in a stage succeed, the pipeline moves on to the next stage.

If any job in a stage fails, the next stage is not (usually) executed and the pipeline ends early.

Pipeline Schedules

Pipelines are normally run based on certain conditions being met. For example, when a branch is pushed to repository.

Pipeline schedules can be used to also run pipelines at specific intervals. For example:

  • Every month on the 22nd (cron example: 0 0 22 * *) for a certain branch.
  • Every month on the 2nd Monday (cron example: 0 0 * * 1#2).

Trigger Pipelines

You can use cURL to trigger pipelines with the pipeline triggers API endpoint. For example:

Use a multiline cURL command:

curl --request POST \
     --form token=<token> \
     --form ref=<ref_name> \