- Getting started
- Feature set
GitLab CI/CD is a tool built into GitLab for software development through the continuous methodologies:
- Continuous Integration (CI)
- Continuous Delivery (CD)
- Continuous Deployment (CD)
Continuous Integration works by pushing small code chunks to your application’s code base hosted in a Git repository, and, to every push, run a pipeline of scripts to build, test, and validate the code changes before merging them into the main branch.
Continuous Delivery and Deployment consist of a step further CI, deploying your application to production at every push to the default branch of the repository.
These methodologies allow you to catch bugs and errors early in the development cycle, ensuring that all the code deployed to production complies with the code standards you established for your app.
For a complete overview of these methodologies and GitLab CI/CD, read the Introduction to CI/CD with GitLab.
For a video demonstration of GitLab CI/CD, see Demo: CI/CD with GitLab.
GitLab CI/CD is configured by a file called
at the repository’s root. The scripts set in this file are executed
by the GitLab Runner.
To get started with GitLab CI/CD, we recommend you read through the following documents:
- How GitLab CI/CD works.
- Fundamental pipeline architectures.
- GitLab CI/CD basic workflow.
- Step-by-step guide for writing
.gitlab-ci.ymlfor the first time.
If you’re coming over from Jenkins, you can also check out our handy reference for converting your pipelines.
You can also get started by using one of the
available through the UI. You can use them by creating a new file,
choosing a template that suits your application, and adjusting it
to your needs:
For a broader overview, see the CI/CD getting started guide.
Once you’re familiar with how GitLab CI/CD works, see the
.gitlab-ci.yml full reference
for all the attributes you can set and use.
GitLab CI/CD supports numerous configuration options:
|Pipelines||Structure your CI/CD process through pipelines.|
|Environment variables||Reuse values based on a variable/value key pair.|
|Environments||Deploy your application to different environments (e.g., staging, production).|
|Job artifacts||Output, use, and reuse job artifacts.|
|Cache dependencies||Cache your dependencies for a faster execution.|
|Schedule pipelines||Schedule pipelines to run as often as you need.|
|Custom path for ||Define a custom path for the CI/CD configuration file.|
|Git submodules for CI/CD||Configure jobs for using Git submodules.|
|SSH keys for CI/CD||Using SSH keys in your CI pipelines.|
|Pipelines triggers||Trigger pipelines through the API.|
|Pipelines for Merge Requests||Design a pipeline structure for running a pipeline in merge requests.|
|Integrate with Kubernetes clusters||Connect your project to Google Kubernetes Engine (GKE) or an existing Kubernetes cluster.|
|GitLab Runner||Configure your own GitLab Runners to execute your scripts.|
|Optimize GitLab and Runner for large repositories||Recommended strategies for handling large repos.|
|All the attributes you can use with GitLab CI/CD.|
Use the vast GitLab CI/CD to easily configure it for specific purposes. Its feature set is listed on the table below according to DevOps stages.
|Auto DevOps||Set up your app’s entire lifecycle.|
|ChatOps||Trigger CI jobs from chat, with results sent back to the channel.|
|Browser Performance Testing||Quickly determine the performance impact of pending code changes.|
|CI services||Link Docker containers with your base image.|
|Code Quality||Analyze your source code quality.|
|GitLab CI/CD for external repositories||Get the benefits of GitLab CI/CD combined with repositories in GitHub and Bitbucket Cloud.|
|Interactive Web Terminals||Open an interactive web terminal to debug the running jobs.|
|JUnit tests||Identify script failures directly on merge requests.|
|Using Docker images||Use GitLab and GitLab Runner with Docker to build and test applications.|
|Auto Deploy||Deploy your application to a production environment in a Kubernetes cluster.|
|Building Docker images||Maintain Docker-based projects using GitLab CI/CD.|
|Canary Deployments||Ship features to only a portion of your pods and let a percentage of your user base to visit the temporarily deployed feature.|
|Deploy Boards||Check the current health and status of each CI/CD environment running on Kubernetes.|
|Feature Flags||Deploy your features behind Feature Flags.|
|GitLab Pages||Deploy static websites.|
|GitLab Releases||Add release notes to Git tags.|
|Review Apps||Configure GitLab CI/CD to preview code changes.|
|Cloud deployment||Deploy your application to a main cloud provider.|
|Container Scanning||Check your Docker containers for known vulnerabilities.|
|Dependency Scanning||Analyze your dependencies for known vulnerabilities.|
|License Compliance||Search your project dependencies for their licenses.|
|Security Test reports||Check for app vulnerabilities.|
Find example project code and tutorials for using GitLab CI/CD with a variety of app frameworks, languages, and platforms on the CI Examples page.
GitLab also provides example projects pre-configured to use GitLab CI/CD.
As a GitLab administrator, you can change the default behavior of GitLab CI/CD for:
The following articles explain reasons to use GitLab CI/CD for your CI/CD infrastructure:
- Why we chose GitLab CI for our CI/CD solution
- Building our web-app on GitLab CI
- 5 Teams that made the switch to GitLab CI/CD
See also the Why CI/CD? presentation.
As GitLab CI/CD has evolved, certain breaking changes have been necessary. These are:
- Use refspec to clone/fetch Git repository.
- Old cache configuration.
- Old metrics server configuration.
- Remove Linux distributions that reach EOL.
- Update command line API for helper images.
- Remove old
- No breaking changes.
- No breaking changes.