GitLab Continuous Integration (GitLab CI/CD)

Pipeline graph

The benefits of Continuous Integration are huge when automation plays an integral part of your workflow. GitLab comes with built-in Continuous Integration, Continuous Deployment, and Continuous Delivery support to build, test, and deploy your application.

Here's some info we've gathered to get you started.

Getting started

The first steps towards your GitLab CI/CD journey.

  • Getting started with GitLab CI/CD: understand how GitLab CI/CD works.
  • GitLab CI/CD configuration file: .gitlab-ci.yml - Learn all about the ins and outs of .gitlab-ci.yml.
  • Pipelines and jobs: configure your GitLab CI/CD pipelines to build, test, and deploy your application.
  • Runners: The GitLab Runner is responsible by running the jobs in your CI/CD pipeline. On, Shared Runners are enabled by default, so you don't need to set up anything to start to use them with GitLab CI/CD.

Introduction to GitLab CI/CD

Why GitLab CI/CD?

Exploring GitLab CI/CD

Advanced use

Once you get familiar with the basics of GitLab CI/CD, it's time to dive in and learn how to leverage its potential even more.

GitLab CI/CD for Docker

Leverage the power of Docker to run your CI pipelines.

Review Apps

Auto DevOps

  • Auto DevOps: Auto DevOps automatically detects, builds, tests, deploys, and monitors your applications.

GitLab CI for GitLab Pages

See the documentation on GitLab Pages.


Check the GitLab CI/CD examples for a collection of tutorials and guides on setting up your CI/CD pipeline for various programming languages, frameworks, and operating systems.


Special configuration (GitLab admin)

As a GitLab administrator, you can change the default behavior of GitLab CI/CD in your whole GitLab instance as well as in each project.

Breaking changes