GitLab CI/CD

GitLab CI/CD is a tool for software development using the continuous methodologies:

note
Out-of-the-box management systems can decrease hours spent on maintaining toolchains by 10% or more. Watch our “Mastering continuous software development” webcast to learn about continuous methods and how GitLab CI/CD can help you simplify and scale software development.

Use GitLab CI/CD to catch bugs and errors early in the development cycle. Ensure that all the code deployed to production complies with the code standards you established for your app.

GitLab CI/CD can automatically build, test, deploy, and monitor your applications by using Auto DevOps.

For a complete overview of these methodologies and GitLab CI/CD, read the Introduction to CI/CD with GitLab.

Video demonstration of continuous integration with GitLab CI/CD: Continuous Integration with GitLab (overview demo).

Concepts

GitLab CI/CD uses a number of concepts to describe and run your build and deploy.

ConceptDescription
PipelinesStructure your CI/CD process through pipelines.
CI/CD variablesReuse values based on a variable/value key pair.
EnvironmentsDeploy your application to different environments (for example, staging, production).
Job artifactsOutput, use, and reuse job artifacts.
Cache dependenciesCache your dependencies for a faster execution.
GitLab RunnerConfigure your own runners to execute your scripts.
Pipeline efficiencyConfigure your pipelines to run quickly and efficiently.
Test casesCreate testing scenarios.

Configuration

GitLab CI/CD supports numerous configuration options:

ConfigurationDescription
Schedule pipelinesSchedule pipelines to run as often as you need.
Custom path for .gitlab-ci.ymlDefine a custom path for the CI/CD configuration file.
Git submodules for CI/CDConfigure jobs for using Git submodules.
SSH keys for CI/CDUsing SSH keys in your CI pipelines.
Pipeline triggersTrigger pipelines through the API.
Merge request pipelinesDesign a pipeline structure for running a pipeline in merge requests.
Integrate with Kubernetes clustersConnect your project to Google Kubernetes Engine (GKE) or an existing Kubernetes cluster.
Optimize GitLab and GitLab Runner for large repositoriesRecommended strategies for handling large repositories.
.gitlab-ci.yml full referenceAll the attributes you can use with GitLab CI/CD.

Certain operations can only be performed according to the user and job permissions.

Features

GitLab CI/CD features, grouped by DevOps stage, include:

FeatureDescription 
Configure  
Auto DevOpsSet up your app’s entire lifecycle. 
ChatOpsTrigger CI jobs from chat, with results sent back to the channel. 
Connect to cloud servicesConnect to cloud providers using OpenID Connect (OIDC) to retrieve temporary credentials to access services or secrets. 
Verify  
CI servicesLink Docker containers with your base image. 
GitLab CI/CD for external repositoriesGet the benefits of GitLab CI/CD combined with repositories in GitHub and Bitbucket Cloud. 
Interactive Web TerminalsOpen an interactive web terminal to debug the running jobs. 
Review AppsConfigure GitLab CI/CD to preview code changes. 
Unit test reportsIdentify test failures directly on merge requests. 
Using Docker imagesUse GitLab and GitLab Runner with Docker to build and test applications. 
Release  
Auto DeployDeploy your application to a production environment in a Kubernetes cluster. 
Building Docker imagesMaintain Docker-based projects using GitLab CI/CD. 
Canary DeploymentsShip features to only a portion of your pods and let a percentage of your user base to visit the temporarily deployed feature. 
Deploy boardsCheck the current health and status of each CI/CD environment running on Kubernetes. 
Feature flagsDeploy your features behind Feature flags. 
GitLab PagesDeploy static websites. 
GitLab ReleasesAdd release notes to Git tags. 
Cloud deploymentDeploy your application to a main cloud provider. 
Secure  
Code QualityAnalyze your source code quality. 
Container ScanningScan your container images for known vulnerabilities. 
Coverage-guided fuzz testingTest your application’s behavior by providing randomized input. 
Dynamic Application Security TestingTest your application’s runtime behavior for vulnerabilities. 
Dependency ScanningAnalyze your dependencies for known vulnerabilities. 
Infrastructure as Code scanningScan your IaC configuration files for known vulnerabilities. 
License ScanningSearch your project dependencies for their licenses.Search your project dependencies for their licenses.
Secret DetectionSearch your application’s source code for secrets. 
Static Application Security TestingTest your application’s source code for known vulnerabilities. 
Web API fuzz testingTest your application’s API behavior by providing randomized input. 
Govern  
Compliance frameworksEnforce a GitLab CI/CD configuration on all projects in a group. 
Scan execution policiesEnforce security scans run on a specified schedule or with the project pipeline. 
Scan results policiesEnforce action based on results of a pipeline security scan. 

Examples

See the CI/CD examples page for example project code and tutorials for using GitLab CI/CD with various:

  • App frameworks
  • Languages
  • Platforms

Administration

You can change the default behavior of GitLab CI/CD for:

See also:

See also the Why CI/CD? presentation.

Major version changes (breaking)

As GitLab CI/CD has evolved, certain breaking changes have been necessary.

For GitLab 15.0 and later, all breaking changes are documented on the following pages:

The breaking changes for GitLab Runner in earlier major version releases are: