GitLab Continuous Integration (CI) & Continuous Delivery (CD)

GitLab CI/CD pipelines build, test, deploy, and monitor your code as part of a single, integrated workflow

Continuous Integration is built-in to GitLab

Continuous Integration (CI) works to integrate code provided by your team in a shared repository. Developers share the new code in a Merge (Pull) Request. The request triggers a pipeline to build, test, and validate the new code prior to merging the changes within your repository.

The practice of Continuous Delivery (CD) ensures the delivery of CI validated code to your application by means of a structured deployment pipeline.

Together, CI and CD act to accelerate how quickly your team can deliver results for your customers and stakeholders. CI helps you catch and reduce bugs early in the development cycle, and CD moves verified code to your applications faster.

CI and CD must work seamlessly together in order for your team to build fast and effectively, as well as being critical to ensuring a fully optimized development practice.

Cited as a Leader in the Forrester CI Wave™

“GitLab supports development teams with a well-documented installation and configuration processes, an easy-to-follow UI, and a flexible per-seat pricing model that supports self service. GitLab’s vision is to serve enterprise-scale, integrated software development teams that want to spend more time writing code and less time maintaining their tool chain.” - Forrester CI Wave™

Get the report

What is CI?

Continuous Integration is the practice of merging all the code that is being produced by developers. The merging usually takes place several times a day in a shared repository. From within the repository, or production environment, building and automated testing are carried out that ensure no integration issues and the early identification of any problems.

What is CD?

Continuous Delivery adds that the software can be released to production at any time, often by automatically pushing changes to a staging system.

Continuous Deployment goes further and pushes changes to production automatically.

Why your team needs a CI/CD workflow

Continuous Integration

Detects errors as quickly as possible: fix problems while fresh in developers mind
Reduces integration problems: smaller problems are easier to digest
Avoid compounding problems: allows teams to develop faster, with more confidence

Continuous Delivery

Ensures every change is releasable: test everything, including deployment, before calling it done
Lowers risk of each release: makes releases “boring”
Delivers value more frequently: reliable deployments mean more releases
Tight customer feedback loops: fast and frequent customer feedback on changes

What are the advantages of GitLab CI/CD?

Integrated: GitLab CI/CD is part of GitLab, enabling a single conversation from planning to deployment (and beyond)
Open source: CI/CD is a part of both the open source GitLab Community Edition and the proprietary GitLab Enterprise Edition
Easy to learn: See our Quick Start guide
Seamless: Part of the single GitLab application, with a single great user experience
Scalable: Tests run distributed on separate machines of which you can add as many as you want
Faster results: Each build can be split in multiple jobs that run in parallel on multiple machines
Optimized for delivery: multiple stages, manual deploy gates, environments, and variables

Features

Multi-platform: you can execute builds on Unix, Windows, macOS, and any other platform that supports Go.
Multi-language: build scripts are command line driven and work with Java, PHP, Ruby, C, and any other language.
Stable: your builds run on a different machine than GitLab.
Parallel builds: GitLab CI/CD splits builds over multiple machines, for fast execution.
Realtime logging: a link in the merge request takes you to the current build log that updates dynamically.
Flexible pipelines: you can define multiple parallel jobs per stage and you can trigger other builds.
Versioned pipelines: a .gitlab-ci.yml file contains your tests and overall process steps, allowing everyone to contribute changes and ensuring every branch gets the pipeline it needs.
Autoscaling: you can automatically spin up and down VM's to make sure your builds get processed immediately and minimize costs.
Build artifacts: you can upload binaries and other build artifacts to GitLab and browse and download them.
Test locally there are multiple executors and you can reproduce tests locally.
Docker support: you can use custom Docker images, spin up services as part of testing, build new Docker images, even run on Kubernetes.
Container Registry: built-in container registry to store, share, and use container images.
Protected variables: securely store and use secrets during deployments using per environment protected variables
Environments: define multiple environments including temporary Review Apps , see deployment history for every environment.

GitLab is one application for the entire DevOps lifecycle

Build your application using GitLab Runners
Run unit and integration tests to check if your code is valid
Look at a live preview of your development branch with Review Apps before merging into stable
Deploy to multiple environments like staging and production, and support advanced features such as canary deployments
Monitor performances and status of your application

GitLab CI/CD is built for Cloud Native

Define your CI/CD job environments with immutable Docker container images for consistency and reproducibility
Utilize our Kubernetes integration to enable CI/CD features like AutoDevOps, Deploy Boards, Review Apps and Canary deployments
Use our Cloud Deployment templates to easily deploy to cloud container and Kubernetes environments

Fully integrated with GitLab

Quick project setup: Add projects with a single click, all hooks are set up automatically via the GitLab API.
Merge request integration: See the status of each build within the Merge Request in GitLab.

Architecture

GitLab CI/CD is a part of GitLab, a web application with an API that stores its state in a database. It manages projects/builds and provides a nice user interface, besides all the features of GitLab.

GitLab Runner is an application which processes builds. It can be deployed separately and works with GitLab CI/CD through an API.

In order to run tests, you need at least one GitLab instance and one GitLab Runner.

GitLab Runner

To perform the actual build, you need to install GitLab Runner which is written in Go.

It can run on any platform for which you can build Go binaries, including Linux, macOS, Windows, FreeBSD and Docker.

It can test any programming language including .Net, Java, Python, C, PHP and others.

GitLab Runner has many features, including autoscaling, great Docker support, and the ability to run multiple jobs concurrently.

Install GitLab Runner

Help and More Information

Please see Get help for GitLab if you have questions
View a step-by-step guide to migrate from Jenkins to GitLab
Propose and discuss new features of CI/CD in the GitLab issue tracker and tag them with the 'CI/CD' label
More information can be found in the GitLab CI/CD documentation
Since version 8.0, GitLab CE/EE and GitLab CI/CD are a single product
See the presentation on Why CI/CD?