GitLab CI/CD variables are key-value pairs you use to store and pass configuration settings and sensitive information, like passwords or API keys, to jobs in a pipeline. Use CI/CD variables to customize jobs by making values defined elsewhere accessible to jobs.

This document lists the configuration options for the GitLab .gitlab-ci.yml file. This file is where you define the CI/CD jobs that make up your pipeline. If you are already familiar with basic CI/CD concepts, try creating your own .gitlab-ci.yml file by following a tutorial that demonstrates a simple or complex pipeline.

This includes a quick introduction to GitLab, the first steps with CI/CD, building a Go project, running tests, using the CI/CD pipeline editor, detecting secrets and security vulnerabilities and offers more exercises for asynchronous practice.

CI/CD pipelines are the fundamental component of GitLab CI/CD. Pipelines are configured in a .gitlab-ci.yml file by using YAML keywords . Pipelines can run automatically for specific events, like when pushing to a branch, creating a merge request, or on a schedule.

This page contains links to a variety of examples that can help you understand how to implement GitLab CI/CD for your specific use case. Examples are available in several forms. As a collection of:

The GitLab-maintained Go component provides an example for a successful migration from a Go CI/CD template, enhanced with inputs and component best practices. You can inspect the Git history to learn more.

Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated Predefined CI/CD variables are available in every GitLab CI/CD pipeline. Avoid overriding predefined variables, as it can cause the pipeline to behave unexpectedly.

CI/CD jobs are the fundamental elements of a GitLab CI/CD pipeline. Jobs are configured in the .gitlab-ci.yml file with a list of commands to execute to accomplish tasks like building, testing, or deploying code.

Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated Use the workflow keyword to control when pipelines are created. The workflow keyword is evaluated before jobs.

GitLab CI/CD makes a set of predefined CI/CD variables available for use in pipeline configuration and job scripts. These variables contain information about the job, pipeline, and other values you might need when the pipeline is triggered or running.