debian-mirror-gitlab/doc/ci/yaml/README.md

4860 lines
168 KiB
Markdown
Raw Normal View History

2019-09-04 21:01:54 +05:30
---
2020-06-23 00:09:42 +05:30
stage: Verify
group: Continuous Integration
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
2019-09-04 21:01:54 +05:30
type: reference
---
2020-07-28 23:09:34 +05:30
# GitLab CI/CD pipeline configuration reference
2015-09-25 12:07:36 +05:30
2020-04-08 14:13:33 +05:30
GitLab CI/CD [pipelines](../pipelines/index.md) are configured using a YAML file called `.gitlab-ci.yml` within each project.
2016-06-02 11:05:42 +05:30
2019-07-07 11:18:12 +05:30
The `.gitlab-ci.yml` file defines the structure and order of the pipelines and determines:
2018-05-09 12:01:36 +05:30
2019-07-07 11:18:12 +05:30
- What to execute using [GitLab Runner](https://docs.gitlab.com/runner/).
- What decisions to make when specific conditions are encountered. For example, when a process succeeds or fails.
This topic covers CI/CD pipeline configuration. For other CI/CD configuration information, see:
- [GitLab CI/CD Variables](../variables/README.md), for configuring the environment the pipelines run in.
- [GitLab Runner advanced configuration](https://docs.gitlab.com/runner/configuration/advanced-configuration.html), for configuring GitLab Runner.
We have complete examples of configuring pipelines:
2020-04-22 19:07:51 +05:30
- For a quick introduction to GitLab CI/CD, follow our [quick start guide](../quick_start/README.md).
2019-07-07 11:18:12 +05:30
- For a collection of examples, see [GitLab CI/CD Examples](../examples/README.md).
2019-12-21 20:55:43 +05:30
- To see a large `.gitlab-ci.yml` file used in an enterprise, see the [`.gitlab-ci.yml` file for `gitlab`](https://gitlab.com/gitlab-org/gitlab/blob/master/.gitlab-ci.yml).
2016-06-02 11:05:42 +05:30
2020-06-23 00:09:42 +05:30
> For some additional information about GitLab CI/CD:
>
> - <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>&nbsp;Watch the [CI/CD Ease of configuration](https://www.youtube.com/embed/opdLqwz6tcE) video.
> - Watch the [Making the case for CI/CD in your organization](https://about.gitlab.com/compare/github-actions-alternative/)
> webcast to learn the benefits of CI/CD and how to measure the results of CI/CD automation.
> - <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>&nbsp;Learn how [Verizon reduced rebuilds](https://about.gitlab.com/blog/2019/02/14/verizon-customer-story/)
> from 30 days to under 8 hours with GitLab.
2020-11-24 15:15:51 +05:30
If you have a [mirrored repository that GitLab pulls from](../../user/project/repository/repository_mirroring.md#pulling-from-a-remote-repository),
2021-01-03 14:25:43 +05:30
you may need to enable pipeline triggering. Go to your project's **Settings > Repository > Pull from a remote repository > Trigger pipelines for mirror updates**.
2016-06-02 11:05:42 +05:30
2019-07-07 11:18:12 +05:30
## Introduction
2015-12-23 02:04:40 +05:30
2019-07-07 11:18:12 +05:30
Pipeline configuration begins with jobs. Jobs are the most fundamental element of a `.gitlab-ci.yml` file.
Jobs are:
- Defined with constraints stating under what conditions they should be executed.
- Top-level elements with an arbitrary name and must contain at least the [`script`](#script) clause.
- Not limited in how many can be defined.
For example:
2015-09-25 12:07:36 +05:30
```yaml
job1:
script: "execute-script-for-job1"
job2:
script: "execute-script-for-job2"
```
2018-05-09 12:01:36 +05:30
The above example is the simplest possible CI/CD configuration with two separate
2015-12-23 02:04:40 +05:30
jobs, where each of the jobs executes a different command.
Of course a command can execute code directly (`./configure;make;make install`)
or run a script (`test.sh`) in the repository.
2015-09-25 12:07:36 +05:30
2020-10-24 23:57:45 +05:30
Jobs are picked up by [runners](../runners/README.md) and executed within the
environment of the runner. What is important is that each job is run
2017-08-17 22:00:37 +05:30
independently from each other.
2015-09-25 12:07:36 +05:30
2019-12-21 20:55:43 +05:30
### Validate the `.gitlab-ci.yml`
2019-07-07 11:18:12 +05:30
2020-04-22 19:07:51 +05:30
Each instance of GitLab CI/CD has an embedded debug tool called Lint, which validates the
2019-07-07 11:18:12 +05:30
content of your `.gitlab-ci.yml` files. You can find the Lint under the page `ci/lint` of your
2019-07-31 22:56:46 +05:30
project namespace. For example, `https://gitlab.example.com/gitlab-org/project-123/-/ci/lint`.
2019-07-07 11:18:12 +05:30
### Unavailable names for jobs
2018-05-09 12:01:36 +05:30
Each job must have a unique name, but there are a few **reserved `keywords` that
2020-05-24 23:13:21 +05:30
can't be used as job names**:
2015-09-25 12:07:36 +05:30
2018-05-09 12:01:36 +05:30
- `image`
- `services`
- `stages`
- `types`
- `before_script`
- `after_script`
- `variables`
- `cache`
2020-01-01 13:55:28 +05:30
- `include`
2015-09-25 12:07:36 +05:30
2019-07-07 11:18:12 +05:30
### Using reserved keywords
If you get validation error when using specific values (for example, `true` or `false`), try to:
- Quote them.
- Change them to a different form. For example, `/bin/true`.
## Configuration parameters
A job is defined as a list of parameters that define the job's behavior.
The following table lists available parameters for jobs:
2020-05-24 23:13:21 +05:30
| Keyword | Description |
|:---------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
2020-10-24 23:57:45 +05:30
| [`script`](#script) | Shell script that is executed by a runner. |
2020-05-24 23:13:21 +05:30
| [`after_script`](#before_script-and-after_script) | Override a set of commands that are executed after job. |
2020-10-24 23:57:45 +05:30
| [`allow_failure`](#allow_failure) | Allow job to fail. Failed job does not contribute to commit status. |
2021-01-03 14:25:43 +05:30
| [`artifacts`](#artifacts) | List of files and directories to attach to a job on success. Also available: `artifacts:paths`, `artifacts:exclude`, `artifacts:expose_as`, `artifacts:name`, `artifacts:untracked`, `artifacts:when`, `artifacts:expire_in`, and `artifacts:reports`. |
2020-10-24 23:57:45 +05:30
| [`before_script`](#before_script-and-after_script) | Override a set of commands that are executed before job. |
2021-01-03 14:25:43 +05:30
| [`cache`](#cache) | List of files that should be cached between subsequent runs. Also available: `cache:paths`, `cache:key`, `cache:untracked`, `cache:when`, and `cache:policy`. |
2020-05-24 23:13:21 +05:30
| [`coverage`](#coverage) | Code coverage settings for a given job. |
2020-10-24 23:57:45 +05:30
| [`dependencies`](#dependencies) | Restrict which artifacts are passed to a specific job by providing a list of jobs to fetch artifacts from. |
2021-01-03 14:25:43 +05:30
| [`environment`](#environment) | Name of an environment to which the job deploys. Also available: `environment:name`, `environment:url`, `environment:on_stop`, `environment:auto_stop_in`, and `environment:action`. |
2020-10-24 23:57:45 +05:30
| [`except`](#onlyexcept-basic) | Limit when jobs are not created. Also available: [`except:refs`, `except:kubernetes`, `except:variables`, and `except:changes`](#onlyexcept-advanced). |
| [`extends`](#extends) | Configuration entries that this job inherits from. |
| [`image`](#image) | Use Docker images. Also available: `image:name` and `image:entrypoint`. |
| [`include`](#include) | Allows this job to include external YAML files. Also available: `include:local`, `include:file`, `include:template`, and `include:remote`. |
| [`interruptible`](#interruptible) | Defines if a job can be canceled when made redundant by a newer run. |
| [`only`](#onlyexcept-basic) | Limit when jobs are created. Also available: [`only:refs`, `only:kubernetes`, `only:variables`, and `only:changes`](#onlyexcept-advanced). |
| [`pages`](#pages) | Upload the result of a job to use with GitLab Pages. |
| [`parallel`](#parallel) | How many instances of a job should be run in parallel. |
| [`release`](#release) | Instructs the runner to generate a [Release](../../user/project/releases/index.md) object. |
| [`resource_group`](#resource_group) | Limit job concurrency. |
2020-05-24 23:13:21 +05:30
| [`retry`](#retry) | When and how many times a job can be auto-retried in case of a failure. |
2020-10-24 23:57:45 +05:30
| [`rules`](#rules) | List of conditions to evaluate and determine selected attributes of a job, and whether or not it's created. May not be used alongside `only`/`except`. |
| [`services`](#services) | Use Docker services images. Also available: `services:name`, `services:alias`, `services:entrypoint`, and `services:command`. |
| [`stage`](#stage) | Defines a job stage (default: `test`). |
| [`tags`](#tags) | List of tags that are used to select a runner. |
2020-05-24 23:13:21 +05:30
| [`timeout`](#timeout) | Define a custom job-level timeout that takes precedence over the project-wide setting. |
| [`trigger`](#trigger) | Defines a downstream pipeline trigger. |
| [`variables`](#variables) | Define job variables on a job level. |
2020-10-24 23:57:45 +05:30
| [`when`](#when) | When to run job. Also available: `when:manual` and `when:delayed`. |
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
## Global parameters
Some parameters must be defined at a global level, affecting all jobs in the pipeline.
### Global defaults
2019-09-30 21:07:59 +05:30
Some parameters can be set globally as the default for all jobs using the
`default:` keyword. Default parameters can then be overridden by job-specific
configuration.
The following job parameters can be defined inside a `default:` block:
- [`image`](#image)
- [`services`](#services)
- [`before_script`](#before_script-and-after_script)
- [`after_script`](#before_script-and-after_script)
2020-01-01 13:55:28 +05:30
- [`tags`](#tags)
2019-09-30 21:07:59 +05:30
- [`cache`](#cache)
2020-01-01 13:55:28 +05:30
- [`artifacts`](#artifacts)
- [`retry`](#retry)
- [`timeout`](#timeout)
2019-12-26 22:10:19 +05:30
- [`interruptible`](#interruptible)
2019-09-30 21:07:59 +05:30
In the following example, the `ruby:2.5` image is set as the default for all
jobs except the `rspec 2.6` job, which uses the `ruby:2.6` image:
```yaml
default:
image: ruby:2.5
rspec:
script: bundle exec rspec
rspec 2.6:
image: ruby:2.6
script: bundle exec rspec
```
2020-05-24 23:13:21 +05:30
#### `inherit`
2020-04-08 14:13:33 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/207484) in GitLab 12.9.
2020-04-08 14:13:33 +05:30
You can disable inheritance of globally defined defaults
and variables with the `inherit:` parameter.
To enable or disable the inheritance of all `variables:` or `default:` parameters, use the following format:
- `default: true` or `default: false`
- `variables: true` or `variables: false`
To inherit only a subset of `default:` parameters or `variables:`, specify what
2021-01-03 14:25:43 +05:30
you wish to inherit. Anything not listed is **not** inherited. Use
2020-04-08 14:13:33 +05:30
one of the following formats:
```yaml
inherit:
default: [parameter1, parameter2]
variables: [VARIABLE1, VARIABLE2]
```
Or:
```yaml
inherit:
default:
- parameter1
- parameter2
variables:
- VARIABLE1
- VARIABLE2
```
In the example below:
- `rubocop`:
2021-01-03 14:25:43 +05:30
- inherits: Nothing.
2020-04-08 14:13:33 +05:30
- `rspec`:
2021-01-03 14:25:43 +05:30
- inherits: the default `image` and the `WEBHOOK_URL` variable.
- does **not** inherit: the default `before_script` and the `DOMAIN` variable.
2020-04-08 14:13:33 +05:30
- `capybara`:
2021-01-03 14:25:43 +05:30
- inherits: the default `before_script` and `image`.
- does **not** inherit: the `DOMAIN` and `WEBHOOK_URL` variables.
2020-04-08 14:13:33 +05:30
- `karma`:
2021-01-03 14:25:43 +05:30
- inherits: the default `image` and `before_script`, and the `DOMAIN` variable.
- does **not** inherit: `WEBHOOK_URL` variable.
2020-04-08 14:13:33 +05:30
```yaml
default:
image: 'ruby:2.4'
before_script:
- echo Hello World
variables:
DOMAIN: example.com
WEBHOOK_URL: https://my-webhook.example.com
rubocop:
inherit:
default: false
variables: false
script: bundle exec rubocop
rspec:
inherit:
default: [image]
variables: [WEBHOOK_URL]
script: bundle exec rspec
capybara:
inherit:
variables: false
script: bundle exec capybara
karma:
inherit:
default: true
variables: [DOMAIN]
script: karma
```
2020-05-24 23:13:21 +05:30
### `stages`
2019-07-07 11:18:12 +05:30
2020-07-28 23:09:34 +05:30
`stages` is used to define stages that contain jobs and is defined
globally for the pipeline.
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
The specification of `stages` allows for having flexible multi stage pipelines.
The ordering of elements in `stages` defines the ordering of jobs' execution:
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
1. Jobs of the same stage are run in parallel.
1. Jobs of the next stage are run after the jobs from the previous stage
complete successfully.
Let's consider the following example, which defines 3 stages:
2019-07-07 11:18:12 +05:30
```yaml
2020-05-24 23:13:21 +05:30
stages:
- build
- test
- deploy
2019-07-07 11:18:12 +05:30
```
2020-05-24 23:13:21 +05:30
1. First, all jobs of `build` are executed in parallel.
1. If all jobs of `build` succeed, the `test` jobs are executed in parallel.
1. If all jobs of `test` succeed, the `deploy` jobs are executed in parallel.
1. If all jobs of `deploy` succeed, the commit is marked as `passed`.
1. If any of the previous jobs fails, the commit is marked as `failed` and no
jobs of further stage are executed.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
There are also two edge cases worth mentioning:
1. If no `stages` are defined in `.gitlab-ci.yml`, then the `build`,
`test` and `deploy` are allowed to be used as job's stage by default.
1. If a job does not specify a `stage`, the job is assigned the `test` stage.
### `workflow:rules`
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/29654) in GitLab 12.5
2020-05-24 23:13:21 +05:30
2020-10-24 23:57:45 +05:30
The top-level `workflow:` key applies to the entirety of a pipeline, and
determines whether or not a pipeline is created. It accepts a single
2020-05-24 23:13:21 +05:30
`rules:` key that operates similarly to [`rules:` defined within jobs](#rules),
enabling dynamic configuration of the pipeline.
2020-07-28 23:09:34 +05:30
If you are new to GitLab CI/CD and `workflow: rules`, you may find the [`workflow:rules` templates](#workflowrules-templates) useful.
2020-10-24 23:57:45 +05:30
To define your own `workflow: rules`, the available configuration options are:
2020-07-28 23:09:34 +05:30
- [`if`](#rulesif): Define a rule.
- [`when`](#when): May be set to `always` or `never` only. If not provided, the default value is `always`.
2020-10-24 23:57:45 +05:30
If a pipeline attempts to run but matches no rule, it's dropped and doesn't run.
Use the example rules below exactly as written to allow pipelines that match the rule
to run. Add `when: never` to prevent pipelines that match the rule from running. See
the [common `if` clauses for `rules`](#common-if-clauses-for-rules) for more examples.
| Example rules | Details |
|------------------------------------------------------|-----------------------------------------------------------|
| `if: '$CI_PIPELINE_SOURCE == "merge_request_event"'` | Control when merge request pipelines run. |
| `if: '$CI_PIPELINE_SOURCE == "push"'` | Control when both branch pipelines and tag pipelines run. |
| `if: $CI_COMMIT_TAG` | Control when tag pipelines run. |
| `if: $CI_COMMIT_BRANCH` | Control when branch pipelines run. |
For example, in the following configuration, pipelines run for all `push` events (changes to
branches and new tags). Only push events with `-wip` in the commit message are excluded. Scheduled
pipelines and merge request pipelines don't run, as there's no rule allowing them.
2020-07-28 23:09:34 +05:30
```yaml
workflow:
rules:
2020-11-24 15:15:51 +05:30
- if: $CI_COMMIT_MESSAGE =~ /-wip$/
2020-07-28 23:09:34 +05:30
when: never
2020-10-24 23:57:45 +05:30
- if: '$CI_PIPELINE_SOURCE == "push"'
```
This example has strict rules, and no other pipelines can run.
Alternatively, you can have loose rules by using only `when: never` rules, followed
by a final `when: always` rule. This allows all types of pipelines, except for any
that match the `when: never` rules:
```yaml
workflow:
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule"'
when: never
- if: '$CI_PIPELINE_SOURCE == "push"'
2020-07-28 23:09:34 +05:30
when: never
- when: always
```
2020-10-24 23:57:45 +05:30
This example never allows pipelines for schedules or `push` (branches and tags) pipelines,
but does allow pipelines in **all** other cases, *including* merge request pipelines.
2021-01-03 14:25:43 +05:30
Be careful not to use a configuration that might run
merge request pipelines and branch pipelines at the same time. As with `rules` defined in jobs,
it can cause [duplicate pipelines](#prevent-duplicate-pipelines).
2020-10-24 23:57:45 +05:30
2020-05-24 23:13:21 +05:30
#### `workflow:rules` templates
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/217732) in GitLab 13.0.
2021-01-03 14:25:43 +05:30
We provide templates that set up `workflow: rules`
for common scenarios. These templates help prevent duplicate pipelines.
2020-05-24 23:13:21 +05:30
The [`Branch-Pipelines` template](https://gitlab.com/gitlab-org/gitlab/-/tree/master/lib/gitlab/ci/templates/Workflows/Branch-Pipelines.gitlab-ci.yml)
makes your pipelines run for branches and tags.
2021-01-03 14:25:43 +05:30
Branch pipeline status is displayed within merge requests that use the branch
as a source. However, this pipeline type does not support any features offered by
[Merge Request Pipelines](../merge_request_pipelines/), like
2020-11-24 15:15:51 +05:30
[Pipelines for Merge Results](../merge_request_pipelines/#pipelines-for-merged-results)
2020-05-24 23:13:21 +05:30
or [Merge Trains](../merge_request_pipelines/pipelines_for_merged_results/merge_trains/).
Use this template if you are intentionally avoiding those features.
It is [included](#include) as follows:
2019-07-07 11:18:12 +05:30
```yaml
2020-05-24 23:13:21 +05:30
include:
- template: 'Workflows/Branch-Pipelines.gitlab-ci.yml'
```
The [`MergeRequest-Pipelines` template](https://gitlab.com/gitlab-org/gitlab/-/tree/master/lib/gitlab/ci/templates/Workflows/MergeRequest-Pipelines.gitlab-ci.yml)
makes your pipelines run for the default branch (usually `master`), tags, and
all types of merge request pipelines. Use this template if you use any of the
the [Pipelines for Merge Requests features](../merge_request_pipelines/), as mentioned
above.
It is [included](#include) as follows:
```yaml
include:
- template: 'Workflows/MergeRequest-Pipelines.gitlab-ci.yml'
```
### `include`
> - Introduced in [GitLab Premium](https://about.gitlab.com/pricing/) 10.5.
2021-01-03 14:25:43 +05:30
> - Available for Starter, Premium, and Ultimate in GitLab 10.6 and later.
2020-05-24 23:13:21 +05:30
> - [Moved](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/42861) to GitLab Core in 11.4.
Using the `include` keyword allows the inclusion of external YAML files. This helps
to break down the CI/CD configuration into multiple files and increases readability for long configuration files.
It's also possible to have template files stored in a central repository and projects include their
configuration files. This helps avoid duplicated configuration, for example, global default variables for all projects.
`include` requires the external YAML file to have the extensions `.yml` or `.yaml`,
2020-10-24 23:57:45 +05:30
otherwise the external file is not included.
2020-05-24 23:13:21 +05:30
2021-01-03 14:25:43 +05:30
Using [YAML anchors](#anchors) across different YAML files sourced by `include` is not
supported. You must only refer to anchors in the same file. Instead
of using YAML anchors, you can use the [`extends` keyword](#extends).
2020-05-24 23:13:21 +05:30
`include` supports the following inclusion methods:
| Method | Description |
|:--------------------------------|:------------------------------------------------------------------|
| [`local`](#includelocal) | Include a file from the local project repository. |
| [`file`](#includefile) | Include a file from a different project repository. |
| [`remote`](#includeremote) | Include a file from a remote URL. Must be publicly accessible. |
2020-10-24 23:57:45 +05:30
| [`template`](#includetemplate) | Include templates that are provided by GitLab. |
2020-05-24 23:13:21 +05:30
2020-07-28 23:09:34 +05:30
The `include` methods do not support [variable expansion](../variables/where_variables_can_be_used.md#variables-usage).
2020-05-24 23:13:21 +05:30
`.gitlab-ci.yml` configuration included by all methods is evaluated at pipeline creation.
The configuration is a snapshot in time and persisted in the database. Any changes to
2020-10-24 23:57:45 +05:30
referenced `.gitlab-ci.yml` configuration is not reflected in GitLab until the next pipeline is created.
2019-07-07 11:18:12 +05:30
2020-07-28 23:09:34 +05:30
The files defined by `include` are:
2020-05-24 23:13:21 +05:30
- Deep merged with those in `.gitlab-ci.yml`.
- Always evaluated first and merged with the content of `.gitlab-ci.yml`,
regardless of the position of the `include` keyword.
TIP: **Tip:**
Use merging to customize and override included CI/CD configurations with local
2020-10-24 23:57:45 +05:30
definitions. Local definitions in `.gitlab-ci.yml` override included definitions.
2020-05-24 23:13:21 +05:30
#### `include:local`
`include:local` includes a file from the same repository as `.gitlab-ci.yml`.
It's referenced using full paths relative to the root directory (`/`).
2020-10-24 23:57:45 +05:30
You can only use files that are tracked by Git on the same branch
2020-05-24 23:13:21 +05:30
your configuration file is on. In other words, when using a `include:local`, make
sure that both `.gitlab-ci.yml` and the local file are on the same branch.
2021-01-03 14:25:43 +05:30
Including local files through Git submodules paths is not supported.
2020-10-24 23:57:45 +05:30
All [nested includes](#nested-includes) are executed in the scope of the same project,
2020-05-24 23:13:21 +05:30
so it's possible to use local, project, remote, or template includes.
Example:
2020-01-01 13:55:28 +05:30
```yaml
2020-05-24 23:13:21 +05:30
include:
- local: '/templates/.gitlab-ci-template.yml'
```
2020-10-24 23:57:45 +05:30
Local includes can be used as a replacement for symbolic links that are not followed.
2020-05-24 23:13:21 +05:30
This can be defined as a short local include:
```yaml
include: '.gitlab-ci-production.yml'
```
#### `include:file`
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/53903) in GitLab 11.7.
2020-05-24 23:13:21 +05:30
To include files from another private project under the same GitLab instance,
use `include:file`. This file is referenced using full paths relative to the
root directory (`/`). For example:
```yaml
include:
- project: 'my-group/my-project'
file: '/templates/.gitlab-ci-template.yml'
```
You can also specify `ref`, with the default being the `HEAD` of the project:
```yaml
include:
- project: 'my-group/my-project'
ref: master
file: '/templates/.gitlab-ci-template.yml'
- project: 'my-group/my-project'
ref: v1.0.0
file: '/templates/.gitlab-ci-template.yml'
- project: 'my-group/my-project'
2020-11-24 15:15:51 +05:30
ref: 787123b47f14b552955ca2786bc9542ae66fee5b # Git SHA
2020-05-24 23:13:21 +05:30
file: '/templates/.gitlab-ci-template.yml'
```
2021-01-03 14:25:43 +05:30
All [nested includes](#nested-includes) are executed in the scope of the target project.
This means you can use local (relative to target project), project, remote,
2020-05-24 23:13:21 +05:30
or template includes.
#### `include:remote`
`include:remote` can be used to include a file from a different location,
using HTTP/HTTPS, referenced by using the full URL. The remote file must be
publicly accessible through a simple GET request as authentication schemas
in the remote URL are not supported. For example:
```yaml
include:
- remote: 'https://gitlab.com/awesome-project/raw/master/.gitlab-ci-template.yml'
```
2020-10-24 23:57:45 +05:30
All [nested includes](#nested-includes) are executed without context as public user, so only another remote
2020-05-24 23:13:21 +05:30
or public project, or template, is allowed.
#### `include:template`
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/53445) in GitLab 11.7.
2020-05-24 23:13:21 +05:30
`include:template` can be used to include `.gitlab-ci.yml` templates that are
[shipped with GitLab](https://gitlab.com/gitlab-org/gitlab/tree/master/lib/gitlab/ci/templates).
For example:
```yaml
# File sourced from GitLab's template collection
include:
- template: Auto-DevOps.gitlab-ci.yml
```
Multiple `include:template` files:
```yaml
include:
- template: Android-Fastlane.gitlab-ci.yml
- template: Auto-DevOps.gitlab-ci.yml
2020-01-01 13:55:28 +05:30
```
2020-10-24 23:57:45 +05:30
All [nested includes](#nested-includes) are executed only with the permission of the user,
2020-05-24 23:13:21 +05:30
so it's possible to use project, remote or template includes.
#### Nested includes
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/56836) in GitLab 11.9.
2020-05-24 23:13:21 +05:30
Nested includes allow you to compose a set of includes.
A total of 100 includes is allowed, but duplicate includes are considered a configuration error.
2021-01-03 14:25:43 +05:30
In [GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/issues/28212) and later, the time limit
2020-05-24 23:13:21 +05:30
for resolving all files is 30 seconds.
#### Additional `includes` examples
There is a list of [additional `includes` examples](includes.md) available.
## Parameter details
The following are detailed explanations for parameters used to configure CI/CD pipelines.
2019-07-07 11:18:12 +05:30
### `image`
Used to specify [a Docker image](../docker/using_docker_images.md#what-is-an-image) to use for the job.
For:
2019-12-21 20:55:43 +05:30
- Simple definition examples, see [Define `image` and `services` from `.gitlab-ci.yml`](../docker/using_docker_images.md#define-image-and-services-from-gitlab-ciyml).
2019-07-07 11:18:12 +05:30
- Detailed usage information, refer to [Docker integration](../docker/README.md) documentation.
#### `image:name`
2020-06-23 00:09:42 +05:30
An [extended Docker configuration option](../docker/using_docker_images.md#extended-docker-configuration-options).
2019-07-07 11:18:12 +05:30
For more information, see [Available settings for `image`](../docker/using_docker_images.md#available-settings-for-image).
#### `image:entrypoint`
2020-06-23 00:09:42 +05:30
An [extended Docker configuration option](../docker/using_docker_images.md#extended-docker-configuration-options).
2019-07-07 11:18:12 +05:30
For more information, see [Available settings for `image`](../docker/using_docker_images.md#available-settings-for-image).
2020-05-24 23:13:21 +05:30
#### `services`
2019-07-07 11:18:12 +05:30
Used to specify a [service Docker image](../docker/using_docker_images.md#what-is-a-service), linked to a base image specified in [`image`](#image).
For:
2019-12-21 20:55:43 +05:30
- Simple definition examples, see [Define `image` and `services` from `.gitlab-ci.yml`](../docker/using_docker_images.md#define-image-and-services-from-gitlab-ciyml).
2019-07-07 11:18:12 +05:30
- Detailed usage information, refer to [Docker integration](../docker/README.md) documentation.
2020-04-22 19:07:51 +05:30
- For example services, see [GitLab CI/CD Services](../services/README.md).
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
##### `services:name`
2019-07-07 11:18:12 +05:30
2020-06-23 00:09:42 +05:30
An [extended Docker configuration option](../docker/using_docker_images.md#extended-docker-configuration-options).
2019-07-07 11:18:12 +05:30
2020-04-22 19:07:51 +05:30
For more information, see [Available settings for `services`](../docker/using_docker_images.md#available-settings-for-services).
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
##### `services:alias`
2019-07-07 11:18:12 +05:30
2020-06-23 00:09:42 +05:30
An [extended Docker configuration option](../docker/using_docker_images.md#extended-docker-configuration-options).
2019-07-07 11:18:12 +05:30
2020-04-22 19:07:51 +05:30
For more information, see [Available settings for `services`](../docker/using_docker_images.md#available-settings-for-services).
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
##### `services:entrypoint`
2019-07-07 11:18:12 +05:30
2020-06-23 00:09:42 +05:30
An [extended Docker configuration option](../docker/using_docker_images.md#extended-docker-configuration-options).
2019-07-07 11:18:12 +05:30
2020-04-22 19:07:51 +05:30
For more information, see [Available settings for `services`](../docker/using_docker_images.md#available-settings-for-services).
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
##### `services:command`
2019-07-07 11:18:12 +05:30
2020-06-23 00:09:42 +05:30
An [extended Docker configuration option](../docker/using_docker_images.md#extended-docker-configuration-options).
2019-07-07 11:18:12 +05:30
2020-04-22 19:07:51 +05:30
For more information, see [Available settings for `services`](../docker/using_docker_images.md#available-settings-for-services).
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
### `script`
2018-03-17 18:26:18 +05:30
2020-05-24 23:13:21 +05:30
`script` is the only required keyword that a job needs. It's a shell script
2020-10-24 23:57:45 +05:30
that is executed by the runner. For example:
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
```yaml
job:
script: "bundle exec rspec"
```
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
[YAML anchors for scripts](#yaml-anchors-for-script) are available.
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
This parameter can also contain several commands using an array:
2015-12-23 02:04:40 +05:30
2018-05-09 12:01:36 +05:30
```yaml
job:
script:
2020-05-24 23:13:21 +05:30
- uname -a
- bundle exec rspec
2018-05-09 12:01:36 +05:30
```
2020-10-24 23:57:45 +05:30
Sometimes, `script` commands must be wrapped in single or double quotes.
2021-01-03 14:25:43 +05:30
For example, commands that contain a colon (`:`) must be wrapped in quotes.
The YAML parser needs to interpret the text as a string rather than
2020-05-24 23:13:21 +05:30
a "key: value" pair. Be careful when using special characters:
`:`, `{`, `}`, `[`, `]`, `,`, `&`, `*`, `#`, `?`, `|`, `-`, `<`, `>`, `=`, `!`, `%`, `@`, `` ` ``.
2015-09-25 12:07:36 +05:30
2020-10-24 23:57:45 +05:30
If any of the script commands return an exit code other than zero, the job
fails and further commands are not executed. You can avoid this behavior by
2020-05-24 23:13:21 +05:30
storing the exit code in a variable:
2015-12-23 02:04:40 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
script:
- false || exit_code=$?
- if [ $exit_code -ne 0 ]; then echo "Previous command failed"; fi;
2015-09-25 12:07:36 +05:30
```
2020-05-24 23:13:21 +05:30
#### `before_script` and `after_script`
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 8.7 and requires GitLab Runner v1.2.
2019-12-21 20:55:43 +05:30
2021-01-03 14:25:43 +05:30
`before_script` is used to define commands that should be run before each
2020-05-24 23:13:21 +05:30
job, including deploy jobs, but after the restoration of any [artifacts](#artifacts).
This must be an array.
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
Scripts specified in `before_script` are concatenated with any scripts specified
in the main [`script`](#script), and executed together in a single shell.
2019-12-26 22:10:19 +05:30
2021-01-03 14:25:43 +05:30
`after_script` is used to define commands that run after each
job, including failed jobs. This must be an array. If a job times out or is cancelled,
the `after_script` commands are not executed. Support for executing `after_script`
commands for timed-out or cancelled jobs
[is planned](https://gitlab.com/gitlab-org/gitlab/-/issues/15603).
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
Scripts specified in `after_script` are executed in a new shell, separate from any
`before_script` or `script` scripts. As a result, they:
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
- Have a current working directory set back to the default.
- Have no access to changes done by scripts defined in `before_script` or `script`, including:
- Command aliases and variables exported in `script` scripts.
2020-10-24 23:57:45 +05:30
- Changes outside of the working tree (depending on the runner executor), like
2020-05-24 23:13:21 +05:30
software installed by a `before_script` or `script` script.
- Have a separate timeout, which is hard coded to 5 minutes. See
2020-06-23 00:09:42 +05:30
[related issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2716) for details.
2020-05-24 23:13:21 +05:30
- Don't affect the job's exit code. If the `script` section succeeds and the
2020-10-24 23:57:45 +05:30
`after_script` times out or fails, the job exits with code `0` (`Job Succeeded`).
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
It's possible to overwrite a globally defined `before_script` or `after_script`
if you set it per-job:
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
```yaml
default:
before_script:
- global before script
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
job:
before_script:
- execute this instead of global before script
script:
- my command
after_script:
- execute this after my script
```
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
[YAML anchors for `before_script` and `after_script`](#yaml-anchors-for-before_script-and-after_script) are available.
2020-04-08 14:13:33 +05:30
2020-06-23 00:09:42 +05:30
#### Coloring script output
Script output can be colored using [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code#Colors),
or by running commands or programs that output ANSI escape codes.
For example, using [Bash with color codes](https://misc.flogisoft.com/bash/tip_colors_and_formatting):
```yaml
job:
script:
- echo -e "\e[31mThis text is red,\e[0m but this text isn't\e[31m however this text is red again."
```
You can define the color codes in Shell variables, or even [custom environment variables](../variables/README.md#custom-environment-variables),
which makes the commands easier to read and reusable.
For example, using the same example as above and variables defined in a `before_script`:
```yaml
job:
before_script:
- TXT_RED="\e[31m" && TXT_CLEAR="\e[0m"
script:
- echo -e "${TXT_RED}This text is red,${TXT_CLEAR} but this part isn't${TXT_RED} however this part is again."
- echo "This text is not colored"
```
Or with [PowerShell color codes](https://superuser.com/a/1259916):
```yaml
job:
before_script:
- $esc="$([char]27)"; $TXT_RED="$esc[31m"; $TXT_CLEAR="$esc[0m"
script:
- Write-Host $TXT_RED"This text is red,"$TXT_CLEAR" but this text isn't"$TXT_RED" however this text is red again."
- Write-Host "This text is not colored"
```
2020-10-24 23:57:45 +05:30
#### Multi-line commands
2020-07-28 23:09:34 +05:30
You can split long commands into multi-line commands to improve readability
2020-10-24 23:57:45 +05:30
using [`|` (literal) and `>` (folded) YAML multi-line block scalar indicators](https://yaml-multiline.info/).
2020-07-28 23:09:34 +05:30
CAUTION: **Warning:**
If multiple commands are combined into one command string, only the last command's
2021-01-03 14:25:43 +05:30
failure or success is reported.
[Failures from earlier commands are ignored due to a bug](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/25394).
To work around this,
run each command as a separate `script:` item, or add an `exit 1` command
to each command string.
2020-07-28 23:09:34 +05:30
You can use the `|` (literal) YAML multiline block scalar indicator to write
commands over multiple lines in the `script` section of a job description.
Each line is treated as a separate command.
Only the first command is repeated in the job log, but additional
commands are still executed:
```yaml
job:
script:
- |
echo "First command line."
echo "Second command line."
echo "Third command line."
```
The example above renders in the job log as:
```shell
$ echo First command line # collapsed multi-line command
First command line
Second command line.
Third command line.
```
The `>` (folded) YAML multiline block scalar indicator treats empty lines between
sections as the start of a new command:
```yaml
job:
script:
- >
echo "First command line
is split over two lines."
echo "Second command line."
```
This behaves similarly to writing multiline commands without the `>` or `|` block
scalar indicators:
```yaml
job:
script:
- echo "First command line
is split over two lines."
echo "Second command line."
```
Both examples above render in the job log as:
```shell
$ echo First command line is split over two lines. # collapsed multi-line command
First command line is split over two lines.
Second command line.
```
2020-10-24 23:57:45 +05:30
When you omit the `>` or `|` block scalar indicators, GitLab forms the command
2021-01-03 14:25:43 +05:30
by concatenating non-empty lines. Make sure the lines can run when concatenated.
2020-07-28 23:09:34 +05:30
Shell [here documents](https://en.wikipedia.org/wiki/Here_document) work with the
`|` and `>` operators as well. The example below transliterates the lower case letters
to upper case:
```yaml
job:
script:
- |
tr a-z A-Z << END_TEXT
one two three
four five six
END_TEXT
```
Results in:
```shell
$ tr a-z A-Z << END_TEXT # collapsed multi-line command
ONE TWO THREE
FOUR FIVE SIX
```
2020-10-24 23:57:45 +05:30
#### Custom collapsible sections
See [custom collapsible sections](../pipelines/index.md#custom-collapsible-sections).
2019-07-07 11:18:12 +05:30
### `stage`
2016-01-29 22:53:50 +05:30
2020-10-24 23:57:45 +05:30
`stage` is defined per-job and relies on [`stages`](#stages), which is defined
2018-05-09 12:01:36 +05:30
globally. It allows to group jobs into different stages, and jobs of the same
2019-07-07 11:18:12 +05:30
`stage` are executed in parallel (subject to [certain conditions](#using-your-own-runners)). For example:
2017-09-10 17:25:29 +05:30
```yaml
stages:
2018-05-09 12:01:36 +05:30
- build
2017-09-10 17:25:29 +05:30
- test
2018-05-09 12:01:36 +05:30
- deploy
2017-09-10 17:25:29 +05:30
2019-12-21 20:55:43 +05:30
job 0:
stage: .pre
script: make something useful before build stage
2018-05-09 12:01:36 +05:30
job 1:
stage: build
script: make build dependencies
job 2:
stage: build
script: make build artifacts
job 3:
stage: test
script: make test
job 4:
stage: deploy
script: make deploy
2019-12-21 20:55:43 +05:30
job 5:
stage: .post
script: make something useful at the end of pipeline
2018-05-09 12:01:36 +05:30
```
2020-10-24 23:57:45 +05:30
#### Using your own runners
2015-12-23 02:04:40 +05:30
2020-10-24 23:57:45 +05:30
When you use your own runners, GitLab Runner runs only one job at a time by default. See the
`concurrent` flag in [runner global settings](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section)
for more information.
2018-05-09 12:01:36 +05:30
2020-10-24 23:57:45 +05:30
Jobs run on your own runners in parallel only if:
2015-09-25 12:07:36 +05:30
2020-10-24 23:57:45 +05:30
- Run on different runners.
- The runner's `concurrent` setting has been changed.
2015-09-25 12:07:36 +05:30
2020-05-24 23:13:21 +05:30
#### `.pre` and `.post`
2015-09-25 12:07:36 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/31441) in GitLab 12.4.
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
The following stages are available to every pipeline:
2015-12-23 02:04:40 +05:30
2020-05-24 23:13:21 +05:30
- `.pre`, which is guaranteed to always be the first stage in a pipeline.
- `.post`, which is guaranteed to always be the last stage in a pipeline.
2015-09-25 12:07:36 +05:30
2020-05-24 23:13:21 +05:30
User-defined stages are executed after `.pre` and before `.post`.
2015-12-23 02:04:40 +05:30
2021-01-03 14:25:43 +05:30
A pipeline is not created if all jobs are in `.pre` or `.post` stages.
2020-05-24 23:13:21 +05:30
The order of `.pre` and `.post` can't be changed, even if defined out of order in `.gitlab-ci.yml`.
For example, the following are equivalent configuration:
2015-12-23 02:04:40 +05:30
2020-05-24 23:13:21 +05:30
- Configured in order:
2017-09-10 17:25:29 +05:30
2020-05-24 23:13:21 +05:30
```yaml
stages:
- .pre
- a
- b
- .post
```
2017-09-10 17:25:29 +05:30
2020-05-24 23:13:21 +05:30
- Configured out of order:
2015-09-25 12:07:36 +05:30
2020-05-24 23:13:21 +05:30
```yaml
stages:
- a
- .pre
- b
- .post
```
2015-09-25 12:07:36 +05:30
2020-05-24 23:13:21 +05:30
- Not explicitly configured:
2019-04-03 18:18:56 +05:30
2020-05-24 23:13:21 +05:30
```yaml
stages:
- a
- b
```
2019-04-03 18:18:56 +05:30
2020-05-24 23:13:21 +05:30
### `extends`
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 11.3.
2020-10-24 23:57:45 +05:30
`extends` defines entry names that a job that uses `extends`
inherits from.
2020-05-24 23:13:21 +05:30
It's an alternative to using [YAML anchors](#anchors) and is a little
more flexible and readable:
2015-11-26 14:37:03 +05:30
```yaml
2020-05-24 23:13:21 +05:30
.tests:
script: rake test
stage: test
2015-11-26 14:37:03 +05:30
only:
2020-05-24 23:13:21 +05:30
refs:
- branches
rspec:
extends: .tests
script: rake rspec
only:
variables:
- $RSPEC
2015-11-26 14:37:03 +05:30
```
2015-12-23 02:04:40 +05:30
2020-05-24 23:13:21 +05:30
In the example above, the `rspec` job inherits from the `.tests` template job.
2020-10-24 23:57:45 +05:30
GitLab performs a reverse deep merge based on the keys. GitLab:
2019-07-07 11:18:12 +05:30
2020-10-24 23:57:45 +05:30
- Merges the `rspec` contents into `.tests` recursively.
- Doesn't merge the values of the keys.
2019-02-15 15:39:39 +05:30
2021-01-03 14:25:43 +05:30
The result is this `rspec` job, where `script: rake test` is overwritten by `script: rake rspec`:
2019-02-15 15:39:39 +05:30
```yaml
2020-05-24 23:13:21 +05:30
rspec:
script: rake rspec
stage: test
only:
refs:
- branches
variables:
- $RSPEC
2019-02-15 15:39:39 +05:30
```
2020-05-24 23:13:21 +05:30
If you do want to include the `rake test`, see [`before_script` and `after_script`](#before_script-and-after_script).
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
`.tests` in this example is a [hidden job](#hide-jobs), but it's
possible to inherit from regular jobs as well.
2019-09-04 21:01:54 +05:30
2020-10-24 23:57:45 +05:30
`extends` supports multi-level inheritance. You should avoid using more than 3 levels,
2020-11-24 15:15:51 +05:30
but you can use as many as eleven.
2020-05-24 23:13:21 +05:30
The following example has two levels of inheritance:
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
```yaml
.tests:
only:
- pushes
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
.rspec:
extends: .tests
script: rake rspec
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
rspec 1:
variables:
RSPEC_SUITE: '1'
extends: .rspec
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
rspec 2:
variables:
RSPEC_SUITE: '2'
extends: .rspec
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
spinach:
extends: .tests
script: rake spinach
```
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
In GitLab 12.0 and later, it's also possible to use multiple parents for
2020-07-28 23:09:34 +05:30
`extends`.
#### Merge details
`extends` is able to merge hashes but not arrays.
The algorithm used for merge is "closest scope wins", so
2020-10-24 23:57:45 +05:30
keys from the last member always override anything defined on other
2020-05-24 23:13:21 +05:30
levels. For example:
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
```yaml
.only-important:
2020-07-28 23:09:34 +05:30
variables:
URL: "http://my-url.internal"
IMPORTANT_VAR: "the details"
2020-05-24 23:13:21 +05:30
only:
- master
- stable
tags:
- production
2020-07-28 23:09:34 +05:30
script:
- echo "Hello world!"
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
.in-docker:
2020-07-28 23:09:34 +05:30
variables:
URL: "http://docker-url.internal"
2020-05-24 23:13:21 +05:30
tags:
- docker
image: alpine
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
rspec:
2020-07-28 23:09:34 +05:30
variables:
GITLAB: "is-awesome"
2020-05-24 23:13:21 +05:30
extends:
- .only-important
- .in-docker
script:
- rake rspec
2019-07-07 11:18:12 +05:30
```
2020-05-24 23:13:21 +05:30
This results in the following `rspec` job:
2018-05-09 12:01:36 +05:30
2020-05-24 23:13:21 +05:30
```yaml
rspec:
2020-07-28 23:09:34 +05:30
variables:
URL: "http://docker-url.internal"
IMPORTANT_VAR: "the details"
GITLAB: "is-awesome"
2020-05-24 23:13:21 +05:30
only:
- master
- stable
tags:
- docker
image: alpine
script:
- rake rspec
```
2018-03-17 18:26:18 +05:30
2020-07-28 23:09:34 +05:30
Note that in the example above:
- `variables` sections have been merged but that `URL: "http://my-url.internal"`
has been overwritten by `URL: "http://docker-url.internal"`.
- `tags: ['production']` has been overwritten by `tags: ['docker']`.
- `script` has not been merged but rather `script: ['echo "Hello world!"']` has
been overwritten by `script: ['rake rspec']`. Arrays can be
merged using [YAML anchors](#anchors).
2020-05-24 23:13:21 +05:30
#### Using `extends` and `include` together
2018-03-17 18:26:18 +05:30
2020-05-24 23:13:21 +05:30
`extends` works across configuration files combined with `include`.
2018-03-17 18:26:18 +05:30
2020-05-24 23:13:21 +05:30
For example, if you have a local `included.yml` file:
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
```yaml
.template:
script:
- echo Hello!
```
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
Then, in `.gitlab-ci.yml` you can use it like this:
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
```yaml
include: included.yml
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
useTemplate:
image: alpine
extends: .template
```
2018-05-09 12:01:36 +05:30
2020-10-24 23:57:45 +05:30
This example runs a job called `useTemplate` that runs `echo Hello!` as defined in
2020-05-24 23:13:21 +05:30
the `.template` job, and uses the `alpine` Docker image as defined in the local job.
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
### `rules`
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/27863) in GitLab 12.3.
2020-04-08 14:13:33 +05:30
2020-07-28 23:09:34 +05:30
The `rules` keyword can be used to include or exclude jobs in pipelines.
Rules are evaluated *in order* until the first match. When matched, the job
is either included or excluded from the pipeline, depending on the configuration.
If included, the job also has [certain attributes](#rules-attributes)
added to it.
2019-12-04 20:38:33 +05:30
2020-10-24 23:57:45 +05:30
`rules` replaces [`only/except`](#onlyexcept-basic) and can't be used in conjunction with it.
If you attempt to use both keywords in the same job, the linter returns a
2020-05-24 23:13:21 +05:30
`key may not be used with rules` error.
2019-12-04 20:38:33 +05:30
2020-07-28 23:09:34 +05:30
#### Rules attributes
2019-12-04 20:38:33 +05:30
2020-07-28 23:09:34 +05:30
The job attributes allowed by `rules` are:
2019-12-04 20:38:33 +05:30
2020-07-28 23:09:34 +05:30
- [`when`](#when): If not defined, defaults to `when: on_success`.
- If used as `when: delayed`, `start_in` is also required.
- [`allow_failure`](#allow_failure): If not defined, defaults to `allow_failure: false`.
If a rule evaluates to true, and `when` has any value except `never`, the job is included in the pipeline.
For example:
```yaml
docker build:
script: docker build -t my-image:$CI_COMMIT_REF_SLUG .
rules:
- if: '$CI_COMMIT_BRANCH == "master"'
when: delayed
start_in: '3 hours'
allow_failure: true
```
Additional job configuration may be added to rules in the future. If something
useful is not available, please [open an issue](https://gitlab.com/gitlab-org/gitlab/-/issues).
#### Rules clauses
Available rule clauses are:
| Clause | Description |
|----------------------------|------------------------------------------------------------------------------------------------------------------------------------|
| [`if`](#rulesif) | Add or exclude jobs from a pipeline by evaluating an `if` statement. Similar to [`only:variables`](#onlyvariablesexceptvariables). |
| [`changes`](#ruleschanges) | Add or exclude jobs from a pipeline based on what files are changed. Same as [`only:changes`](#onlychangesexceptchanges). |
| [`exists`](#rulesexists) | Add or exclude jobs from a pipeline based on the presence of specific files. |
2020-04-08 14:13:33 +05:30
2020-07-28 23:09:34 +05:30
Rules are evaluated in order until a match is found. If a match is found, the attributes
are checked to see if the job should be added to the pipeline. If no attributes are defined,
the defaults are:
2020-05-24 23:13:21 +05:30
2020-07-28 23:09:34 +05:30
- `when: on_success`
- `allow_failure: false`
2020-05-24 23:13:21 +05:30
2020-07-28 23:09:34 +05:30
The job is added to the pipeline:
2020-05-24 23:13:21 +05:30
2020-07-28 23:09:34 +05:30
- If a rule matches and has `when: on_success`, `when: delayed` or `when: always`.
- If no rules match, but the last clause is `when: on_success`, `when: delayed`
or `when: always` (with no rule).
The job is not added to the pipeline:
- If no rules match, and there is no standalone `when: on_success`, `when: delayed` or
`when: always`.
- If a rule matches, and has `when: never` as the attribute.
For example, using `if` clauses to strictly limit when jobs run:
2020-04-08 14:13:33 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
script: "echo Hello, Rules!"
rules:
2020-07-28 23:09:34 +05:30
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
2020-05-24 23:13:21 +05:30
when: manual
2020-07-28 23:09:34 +05:30
allow_failure: true
- if: '$CI_PIPELINE_SOURCE == "schedule"'
```
In this example:
- If the pipeline is for a merge request, the first rule matches, and the job
is added to the [merge request pipeline](../merge_request_pipelines/index.md)
with attributes of:
- `when: manual` (manual job)
- `allow_failure: true` (allows the pipeline to continue running even if the manual job is not run)
- If the pipeline is **not** for a merge request, the first rule doesn't match, and the
second rule is evaluated.
- If the pipeline is a scheduled pipeline, the second rule matches, and the job
is added to the scheduled pipeline. Since no attributes were defined, it is added
with:
- `when: on_success` (default)
- `allow_failure: false` (default)
- In **all other cases**, no rules match, so the job is **not** added to any other pipeline.
Alternatively, you can define a set of rules to exclude jobs in a few cases, but
run them in all other cases:
```yaml
job:
script: "echo Hello, Rules!"
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
when: never
- if: '$CI_PIPELINE_SOURCE == "schedule"'
when: never
2020-05-24 23:13:21 +05:30
- when: on_success
2020-04-08 14:13:33 +05:30
```
2020-07-28 23:09:34 +05:30
- If the pipeline is for a merge request, the job is **not** be added to the pipeline.
- If the pipeline is a scheduled pipeline, the job is **not** be added to the pipeline.
- In **all other cases**, the job is added to the pipeline, with `when: on_success`.
CAUTION: **Caution:**
2020-10-24 23:57:45 +05:30
If you use a `when:` clause as the final rule (not including `when: never`), two
2020-07-28 23:09:34 +05:30
simultaneous pipelines may start. Both push pipelines and merge request pipelines can
be triggered by the same event (a push to the source branch for an open merge request).
2020-10-24 23:57:45 +05:30
See how to [prevent duplicate pipelines](#prevent-duplicate-pipelines)
2020-07-28 23:09:34 +05:30
for more details.
2020-10-24 23:57:45 +05:30
#### Prevent duplicate pipelines
2020-07-28 23:09:34 +05:30
2020-10-24 23:57:45 +05:30
Jobs defined with `rules` can trigger multiple pipelines with the same action. You
don't have to explicitly configure rules for each type of pipeline to trigger them
accidentally. Rules that are too loose (allowing too many types of pipelines) could
cause a second pipeline to run unexpectedly.
2020-07-28 23:09:34 +05:30
2020-10-24 23:57:45 +05:30
Some configurations that have the potential to cause duplicate pipelines cause a
[pipeline warning](../troubleshooting.md#pipeline-warnings) to be displayed.
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/219431) in GitLab 13.3.
2020-07-28 23:09:34 +05:30
For example:
```yaml
job:
script: "echo This creates double pipelines!"
rules:
- if: '$CUSTOM_VARIABLE == "false"'
when: never
- when: always
```
This job does not run when `$CUSTOM_VARIABLE` is false, but it *does* run in **all**
other pipelines, including **both** push (branch) and merge request pipelines. With
this configuration, every push to an open merge request's source branch
2020-10-24 23:57:45 +05:30
causes duplicated pipelines.
There are multiple ways to avoid this:
- Use [`workflow: rules`](#workflowrules) to specify which types of pipelines
can run. To eliminate duplicate pipelines, allow only merge request pipelines
or push (branch) pipelines.
- Rewrite the rules to run the job only in very specific cases,
and avoid using a final `when:` rule:
```yaml
job:
script: "echo This does NOT create double pipelines!"
rules:
- if: '$CUSTOM_VARIABLE == "true" && $CI_PIPELINE_SOURCE == "merge_request_event"'
```
You can prevent duplicate pipelines by changing the job rules to avoid either push (branch)
pipelines or merge request pipelines. However, if you use a `- when: always` rule without
`workflow: rules`, GitLab still displays a [pipeline warning](../troubleshooting.md#pipeline-warnings).
For example, the following does not trigger double pipelines, but is not recommended
without `workflow: rules`:
2020-07-28 23:09:34 +05:30
2020-10-24 23:57:45 +05:30
```yaml
job:
script: "echo This does NOT create double pipelines!"
rules:
- if: '$CI_PIPELINE_SOURCE == "push"'
when: never
- when: always
```
2020-07-28 23:09:34 +05:30
2020-10-24 23:57:45 +05:30
Do not include both push and merge request pipelines in the same job:
2020-07-28 23:09:34 +05:30
2020-10-24 23:57:45 +05:30
```yaml
job:
script: "echo This creates double pipelines!"
rules:
- if: '$CI_PIPELINE_SOURCE == "push"'
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
```
Also, do not mix `only/except` jobs with `rules` jobs in the same pipeline.
It may not cause YAML errors, but the different default behaviors of `only/except`
and `rules` can cause issues that are difficult to troubleshoot:
```yaml
job-with-no-rules:
script: "echo This job runs in branch pipelines."
job-with-rules:
script: "echo This job runs in merge request pipelines."
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
```
For every change pushed to the branch, duplicate pipelines run. One
branch pipeline runs a single job (`job-with-no-rules`), and one merge request pipeline
runs the other job (`job-with-rules`). Jobs with no rules default
to [`except: merge_requests`](#onlyexcept-basic), so `job-with-no-rules`
runs in all cases except merge requests.
It is not possible to define rules based on whether or not a branch has an open
merge request associated with it. You can't configure a job to be included in:
- Only branch pipelines when the branch doesn't have a merge request associated with it.
- Only merge request pipelines when the branch has a merge request associated with it.
See the [related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/201845) for more details.
#### `rules:if`
2018-12-05 23:21:45 +05:30
2020-07-28 23:09:34 +05:30
`rules:if` clauses determine whether or not jobs are added to a pipeline by evaluating
a simple `if` statement. If the `if` statement is true, the job is either included
or excluded from a pipeline. In plain English, `if` rules can be interpreted as one of:
2019-07-31 22:56:46 +05:30
2020-07-28 23:09:34 +05:30
- "If this rule evaluates to true, add the job" (default).
- "If this rule evaluates to true, do not add the job" (by adding `when: never`).
2018-03-17 18:26:18 +05:30
2020-05-24 23:13:21 +05:30
`rules:if` differs slightly from `only:variables` by accepting only a single
2020-07-28 23:09:34 +05:30
expression string per rule, rather than an array of them. Any set of expressions to be
2020-10-24 23:57:45 +05:30
evaluated can be [conjoined into a single expression](../variables/README.md#conjunction--disjunction)
by using `&&` or `||`, and use
2020-05-24 23:13:21 +05:30
the [variable matching syntax](../variables/README.md#syntax-of-environment-variable-expressions).
2020-11-24 15:15:51 +05:30
Unlike variables in [`script`](../variables/README.md#syntax-of-environment-variables-in-job-scripts)
sections, variables in rules expressions are always formatted as `$VARIABLE`.
2020-05-24 23:13:21 +05:30
2020-07-28 23:09:34 +05:30
`if:` clauses are evaluated based on the values of [predefined environment variables](../variables/predefined_variables.md)
or [custom environment variables](../variables/README.md#custom-environment-variables).
2020-05-24 23:13:21 +05:30
For example:
2018-03-17 18:26:18 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
script: "echo Hello, Rules!"
rules:
2020-07-28 23:09:34 +05:30
- if: '$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME =~ /^feature/ && $CI_MERGE_REQUEST_TARGET_BRANCH_NAME == "master"'
2020-05-24 23:13:21 +05:30
when: always
2020-07-28 23:09:34 +05:30
- if: '$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME =~ /^feature/'
2020-05-24 23:13:21 +05:30
when: manual
2020-07-28 23:09:34 +05:30
allow_failure: true
2020-11-24 15:15:51 +05:30
- if: '$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME' # Checking for the presence of a variable is possible
2019-02-15 15:39:39 +05:30
```
2020-06-23 00:09:42 +05:30
Some details regarding the logic that determines the `when` for the job:
2020-07-28 23:09:34 +05:30
- If none of the provided rules match, the job is set to `when: never` and is
2020-06-23 00:09:42 +05:30
not included in the pipeline.
- A rule without any conditional clause, such as a `when` or `allow_failure`
rule without `if` or `changes`, always matches, and is always used if reached.
2020-07-28 23:09:34 +05:30
- If a rule matches and has no `when` defined, the rule uses the `when`
2020-06-23 00:09:42 +05:30
defined for the job, which defaults to `on_success` if not defined.
2020-07-28 23:09:34 +05:30
- You can define `when` once per rule, or once at the job-level, which applies to
all rules. You can't mix `when` at the job-level with `when` in rules.
2020-10-24 23:57:45 +05:30
##### Common `if` clauses for `rules`
2020-07-28 23:09:34 +05:30
For behavior similar to the [`only`/`except` keywords](#onlyexcept-basic), you can
2020-10-24 23:57:45 +05:30
check the value of the `$CI_PIPELINE_SOURCE` variable:
| Value | Description |
|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `api` | For pipelines triggered by the [pipelines API](../../api/pipelines.md#create-a-new-pipeline). |
| `chat` | For pipelines created by using a [GitLab ChatOps](../chatops/README.md) command. |
| `external` | When using CI services other than GitLab. |
| `external_pull_request_event` | When an external pull request on GitHub is created or updated. See [Pipelines for external pull requests](../ci_cd_for_external_repos/index.md#pipelines-for-external-pull-requests). |
2020-07-28 23:09:34 +05:30
| `merge_request_event` | For pipelines created when a merge request is created or updated. Required to enable [merge request pipelines](../merge_request_pipelines/index.md), [merged results pipelines](../merge_request_pipelines/pipelines_for_merged_results/index.md), and [merge trains](../merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md). |
2020-10-24 23:57:45 +05:30
| `parent_pipeline` | For pipelines triggered by a [parent/child pipeline](../parent_child_pipelines.md) with `rules`, use this in the child pipeline configuration so that it can be triggered by the parent pipeline. |
| `pipeline` | For [multi-project pipelines](../multi_project_pipelines.md) created by [using the API with `CI_JOB_TOKEN`](../multi_project_pipelines.md#triggering-multi-project-pipelines-through-api), or the [`trigger`](#trigger) keyword. |
| `push` | For pipelines triggered by a `git push` event, including for branches and tags. |
| `schedule` | For [scheduled pipelines](../pipelines/schedules.md). |
| `trigger` | For pipelines created by using a [trigger token](../triggers/README.md#trigger-token). |
| `web` | For pipelines created by using **Run pipeline** button in the GitLab UI, from the project's **CI/CD > Pipelines** section. |
| `webide` | For pipelines created by using the [WebIDE](../../user/project/web_ide/index.md). |
2020-07-28 23:09:34 +05:30
For example:
```yaml
job:
script: "echo Hello, Rules!"
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule"'
when: manual
allow_failure: true
- if: '$CI_PIPELINE_SOURCE == "push"'
```
This example runs the job as a manual job in scheduled pipelines or in push
pipelines (to branches or tags), with `when: on_success` (default). It does not
add the job to any other pipeline type.
Another example:
```yaml
job:
script: "echo Hello, Rules!"
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
- if: '$CI_PIPELINE_SOURCE == "schedule"'
```
This example runs the job as a `when: on_success` job in [merge request pipelines](../merge_request_pipelines/index.md)
and scheduled pipelines. It does not run in any other pipeline type.
2019-02-15 15:39:39 +05:30
2020-07-28 23:09:34 +05:30
Other commonly used variables for `if` clauses:
2019-07-31 22:56:46 +05:30
2020-07-28 23:09:34 +05:30
- `if: $CI_COMMIT_TAG`: If changes are pushed for a tag.
- `if: $CI_COMMIT_BRANCH`: If changes are pushed to any branch.
- `if: '$CI_COMMIT_BRANCH == "master"'`: If changes are pushed to `master`.
- `if: '$CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH'`: If changes are pushed to the default
branch (usually `master`). Useful if reusing the same configuration in multiple
projects with potentially different default branches.
- `if: '$CI_COMMIT_BRANCH =~ /regex-expression/'`: If the commit branch matches a regular expression.
- `if: '$CUSTOM_VARIABLE !~ /regex-expression/'`: If the [custom variable](../variables/README.md#custom-environment-variables)
`CUSTOM_VARIABLE` does **not** match a regular expression.
- `if: '$CUSTOM_VARIABLE == "value1"'`: If the custom variable `CUSTOM_VARIABLE` is
exactly `value1`.
2020-10-24 23:57:45 +05:30
#### `rules:changes`
2020-07-28 23:09:34 +05:30
To determine if jobs should be added to a pipeline, `rules: changes` clauses check
the files changed by Git push events.
`rules: changes` works exactly the same way as [`only: changes` and `except: changes`](#onlychangesexceptchanges),
accepting an array of paths. Similarly, it always returns true if there is no
2020-11-24 15:15:51 +05:30
Git push event, for example, when a new tag is created. It's recommended to use it
only with branch pipelines or merge request pipelines. For example, it's common to
use `rules: changes` with one of the following `if` clauses:
- `if: $CI_COMMIT_BRANCH`
- `if: '$CI_PIPELINE_SOURCE == "merge_request_event"'`
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
For example:
2019-02-15 15:39:39 +05:30
```yaml
2020-07-28 23:09:34 +05:30
workflow:
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
2020-05-24 23:13:21 +05:30
docker build:
script: docker build -t my-image:$CI_COMMIT_REF_SLUG .
rules:
2020-07-28 23:09:34 +05:30
- changes:
- Dockerfile
2020-05-24 23:13:21 +05:30
when: manual
2020-07-28 23:09:34 +05:30
allow_failure: true
2018-03-17 18:26:18 +05:30
```
2020-07-28 23:09:34 +05:30
In this example:
2019-02-15 15:39:39 +05:30
2020-07-28 23:09:34 +05:30
- [`workflow: rules`](#workflowrules) allows only pipelines for merge requests for all jobs.
- If `Dockerfile` has changed, add the job to the pipeline as a manual job, and allow the pipeline
to continue running even if the job is not triggered (`allow_failure: true`).
- If `Dockerfile` has not changed, do not add job to any pipeline (same as `when: never`).
2019-07-31 22:56:46 +05:30
2020-10-24 23:57:45 +05:30
To implement a rule similar to [`except: changes`](#onlychangesexceptchanges),
use `when: never`.
#### `rules:exists`
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/24021) in GitLab 12.4.
2016-06-02 11:05:42 +05:30
2020-10-24 23:57:45 +05:30
`exists` accepts an array of paths and matches if any of these paths exist
2020-05-24 23:13:21 +05:30
as files in the repository.
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
For example:
2019-12-21 20:55:43 +05:30
```yaml
job:
script: docker build -t my-image:$CI_COMMIT_REF_SLUG .
rules:
- exists:
2020-07-28 23:09:34 +05:30
- Dockerfile
2019-12-21 20:55:43 +05:30
```
You can also use glob patterns to match multiple files in any directory within
the repository.
For example:
```yaml
job:
script: bundle exec rspec
rules:
- exists:
2020-07-28 23:09:34 +05:30
- spec/**.rb
2019-12-21 20:55:43 +05:30
```
2021-01-03 14:25:43 +05:30
For performance reasons, using `exists` with patterns is limited to 10,000
checks. After the 10,000th check, rules with patterned globs always match.
2019-12-21 20:55:43 +05:30
2020-10-24 23:57:45 +05:30
#### `rules:allow_failure`
2020-03-13 15:44:24 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/30235) in GitLab 12.8.
2020-03-13 15:44:24 +05:30
You can use [`allow_failure: true`](#allow_failure) within `rules:` to allow a job to fail, or a manual job to
wait for action, without stopping the pipeline itself. All jobs using `rules:` default to `allow_failure: false`
if `allow_failure:` is not defined.
2020-06-23 00:09:42 +05:30
The rule-level `rules:allow_failure` option overrides the job-level
[`allow_failure`](#allow_failure) option, and is only applied when the job is
triggered by the particular rule.
2020-03-13 15:44:24 +05:30
```yaml
job:
script: "echo Hello, Rules!"
rules:
- if: '$CI_MERGE_REQUEST_TARGET_BRANCH_NAME == "master"'
when: manual
allow_failure: true
```
2020-10-24 23:57:45 +05:30
In this example, if the first rule matches, then the job has `when: manual` and `allow_failure: true`.
2020-03-13 15:44:24 +05:30
2019-12-04 20:38:33 +05:30
#### Complex rule clauses
2020-10-24 23:57:45 +05:30
To conjoin `if`, `changes`, and `exists` clauses with an `AND`, use them in the
2019-12-21 20:55:43 +05:30
same rule.
2019-12-04 20:38:33 +05:30
In the following example:
2020-11-24 15:15:51 +05:30
- If the `Dockerfile` file or any file in `/docker/scripts` has changed, and var=blah,
2020-10-24 23:57:45 +05:30
then the job runs manually
- Otherwise, the job isn't included in the pipeline.
2019-12-04 20:38:33 +05:30
```yaml
docker build:
script: docker build -t my-image:$CI_COMMIT_REF_SLUG .
rules:
- if: '$VAR == "string value"'
2021-01-03 14:25:43 +05:30
changes: # Include the job and set to when:manual if any of the follow paths match a modified file.
2020-07-28 23:09:34 +05:30
- Dockerfile
- docker/scripts/*
2019-12-04 20:38:33 +05:30
when: manual
2021-01-03 14:25:43 +05:30
# - when: never would be redundant here, this is implied any time rules are listed.
2019-12-04 20:38:33 +05:30
```
2021-01-03 14:25:43 +05:30
Keywords such as `branches` or `refs` that are available for
`only`/`except` are not available in `rules`. They are being individually
2020-05-24 23:13:21 +05:30
considered for their usage and behavior in this context. Future keyword improvements
are being discussed in our [epic for improving `rules`](https://gitlab.com/groups/gitlab-org/-/epics/2783),
where anyone can add suggestions or requests.
2019-12-04 20:38:33 +05:30
2020-10-24 23:57:45 +05:30
You can use [parentheses](../variables/README.md#parentheses) with `&&` and `||` to build more complicated variable expressions.
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230938) in GitLab 13.3:
```yaml
job1:
script:
- echo This rule uses parentheses.
rules:
if: ($CI_COMMIT_BRANCH == "master" || $CI_COMMIT_BRANCH == "develop") && $MY_VARIABLE
```
2021-01-03 14:25:43 +05:30
CAUTION: **Caution:**
[Before GitLab 13.3](https://gitlab.com/gitlab-org/gitlab/-/issues/230938),
rules that use both `||` and `&&` may evaluate with an unexpected order of operations.
2020-10-24 23:57:45 +05:30
2020-05-24 23:13:21 +05:30
### `only`/`except` (basic)
2019-12-21 20:55:43 +05:30
NOTE: **Note:**
2020-05-24 23:13:21 +05:30
The [`rules`](#rules) syntax is an improved, more powerful solution for defining
when jobs should run or not. Consider using `rules` instead of `only/except` to get
the most out of your pipelines.
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
`only` and `except` are two parameters that set a job policy to limit when
jobs are created:
2018-12-05 23:21:45 +05:30
2020-10-24 23:57:45 +05:30
1. `only` defines the names of branches and tags the job runs for.
1. `except` defines the names of branches and tags the job does
**not** run for.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
There are a few rules that apply to the usage of job policy:
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
- `only` and `except` are inclusive. If both `only` and `except` are defined
in a job specification, the ref is filtered by `only` and `except`.
- `only` and `except` allow the use of regular expressions ([supported regexp syntax](#supported-onlyexcept-regexp-syntax)).
- `only` and `except` allow to specify a repository path to filter jobs for
forks.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
In addition, `only` and `except` allow the use of special keywords:
2018-12-05 23:21:45 +05:30
2020-10-24 23:57:45 +05:30
| **Value** | **Description** |
|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `api` | For pipelines triggered by the [pipelines API](../../api/pipelines.md#create-a-new-pipeline). |
| `branches` | When the Git reference for a pipeline is a branch. |
| `chat` | For pipelines created by using a [GitLab ChatOps](../chatops/README.md) command. |
| `external` | When using CI services other than GitLab. |
| `external_pull_requests` | When an external pull request on GitHub is created or updated (See [Pipelines for external pull requests](../ci_cd_for_external_repos/index.md#pipelines-for-external-pull-requests)). |
| `merge_requests` | For pipelines created when a merge request is created or updated. Enables [merge request pipelines](../merge_request_pipelines/index.md), [merged results pipelines](../merge_request_pipelines/pipelines_for_merged_results/index.md), and [merge trains](../merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.md). |
| `pipelines` | For [multi-project pipelines](../multi_project_pipelines.md) created by [using the API with `CI_JOB_TOKEN`](../multi_project_pipelines.md#triggering-multi-project-pipelines-through-api), or the [`trigger`](#trigger) keyword. |
| `pushes` | For pipelines triggered by a `git push` event, including for branches and tags. |
| `schedules` | For [scheduled pipelines](../pipelines/schedules.md). |
| `tags` | When the Git reference for a pipeline is a tag. |
| `triggers` | For pipelines created by using a [trigger token](../triggers/README.md#trigger-token). |
| `web` | For pipelines created by using **Run pipeline** button in the GitLab UI, from the project's **CI/CD > Pipelines** section. |
2018-12-05 23:21:45 +05:30
2021-01-03 14:25:43 +05:30
In the example below, `job` runs only for refs that start with `issue-`,
whereas all branches are skipped:
2018-12-05 23:21:45 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
# use regexp
only:
- /^issue-.*$/
# use special keyword
except:
- branches
2018-12-05 23:21:45 +05:30
```
2020-05-24 23:13:21 +05:30
Pattern matching is case-sensitive by default. Use `i` flag modifier, like
`/pattern/i` to make a pattern case-insensitive:
2017-08-17 22:00:37 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
# use regexp
only:
- /^issue-.*$/i
# use special keyword
except:
- branches
2017-08-17 22:00:37 +05:30
```
2021-01-03 14:25:43 +05:30
In this example, `job` runs only for refs that are tagged, or if a build is
explicitly requested by an API trigger or a [Pipeline Schedule](../pipelines/schedules.md):
2016-11-03 12:29:30 +05:30
2017-08-17 22:00:37 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
# use special keywords
only:
- tags
- triggers
- schedules
2016-11-03 12:29:30 +05:30
```
2020-05-24 23:13:21 +05:30
The repository path can be used to have jobs executed only for the parent
repository and not forks:
2016-11-03 12:29:30 +05:30
2017-08-17 22:00:37 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
only:
- branches@gitlab-org/gitlab
except:
- master@gitlab-org/gitlab
- /^release/.*$/@gitlab-org/gitlab
2016-11-03 12:29:30 +05:30
```
2020-11-24 15:15:51 +05:30
The above example runs `job` for all branches on `gitlab-org/gitlab`,
2020-05-24 23:13:21 +05:30
except `master` and those with names prefixed with `release/`.
2016-11-03 12:29:30 +05:30
2020-05-24 23:13:21 +05:30
If a job does not have an `only` rule, `only: ['branches', 'tags']` is set by
default. If it does not have an `except` rule, it's empty.
2016-11-03 12:29:30 +05:30
2020-05-24 23:13:21 +05:30
For example,
2016-11-03 12:29:30 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
script: echo 'test'
2016-11-03 12:29:30 +05:30
```
2020-05-24 23:13:21 +05:30
is translated to:
2020-03-13 15:44:24 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
script: echo 'test'
only: ['branches', 'tags']
2020-03-13 15:44:24 +05:30
```
2020-05-24 23:13:21 +05:30
#### Regular expressions
2020-01-01 13:55:28 +05:30
2021-01-03 14:25:43 +05:30
The `@` symbol denotes the beginning of a ref's repository path.
To match a ref name that contains the `@` character in a regular expression,
you must use the hex character code match `\x40`.
2020-01-01 13:55:28 +05:30
2020-05-24 23:13:21 +05:30
Only the tag or branch name can be matched by a regular expression.
The repository path, if given, is always matched literally.
2020-01-01 13:55:28 +05:30
2021-01-03 14:25:43 +05:30
To match the tag or branch name,
the entire ref name part of the pattern must be a regular expression surrounded by `/`.
For example, you can't use `issue-/.*/` to match all tag names or branch names
that begin with `issue-`, but you can use `/issue-.*/`.
Regular expression flags must be appended after the closing `/`.
2020-01-01 13:55:28 +05:30
2020-07-28 23:09:34 +05:30
TIP: **Tip:**
2020-05-24 23:13:21 +05:30
Use anchors `^` and `$` to avoid the regular expression
matching only a substring of the tag name or branch name.
For example, `/^issue-.*$/` is equivalent to `/^issue-/`,
while just `/issue/` would also match a branch called `severe-issues`.
2020-01-01 13:55:28 +05:30
2020-05-24 23:13:21 +05:30
#### Supported `only`/`except` regexp syntax
2020-01-01 13:55:28 +05:30
2021-01-03 14:25:43 +05:30
In GitLab 11.9.4, GitLab began internally converting the regexp used
2020-05-24 23:13:21 +05:30
in `only` and `except` parameters to [RE2](https://github.com/google/re2/wiki/Syntax).
2018-04-04 21:44:52 +05:30
2021-01-03 14:25:43 +05:30
[RE2](https://github.com/google/re2/wiki/Syntax) limits the set of available features
due to computational complexity, and some features, like negative lookaheads, became unavailable.
Only a subset of features provided by [Ruby Regexp](https://ruby-doc.org/core/Regexp.html)
are now supported.
2018-04-04 21:44:52 +05:30
2021-01-03 14:25:43 +05:30
From GitLab 11.9.7 to GitLab 12.0, GitLab provided a feature flag to
let you use the unsafe regexp syntax. This flag allowed
compatibility with the previous syntax version so you could gracefully migrate to the new syntax.
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
```ruby
Feature.enable(:allow_unsafe_ruby_regexp)
2018-04-04 21:44:52 +05:30
```
2020-05-24 23:13:21 +05:30
### `only`/`except` (advanced)
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
GitLab supports both simple and complex strategies, so it's possible to use an
array and a hash configuration scheme.
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
Four keys are available:
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
- `refs`
- `variables`
- `changes`
- `kubernetes`
2018-04-04 21:44:52 +05:30
2021-01-03 14:25:43 +05:30
If you use multiple keys under `only` or `except`, the keys are evaluated as a
2020-05-24 23:13:21 +05:30
single conjoined expression. That is:
2018-04-04 21:44:52 +05:30
2020-11-24 15:15:51 +05:30
- `only:` includes the job if **all** of the keys have at least one condition that matches.
- `except:` excludes the job if **any** of the keys have at least one condition that matches.
2018-04-04 21:44:52 +05:30
2020-11-24 15:15:51 +05:30
With `only`, individual keys are logically joined by an `AND`. A job is added to
the pipeline if the following is true:
2018-04-04 21:44:52 +05:30
2020-11-24 15:15:51 +05:30
- `(any listed refs are true) AND (any listed variables are true) AND (any listed changes are true) AND (any chosen Kubernetes status matches)`
2018-04-04 21:44:52 +05:30
2021-01-03 14:25:43 +05:30
In the example below, the `test` job is `only` created when **all** of the following are true:
2018-04-04 21:44:52 +05:30
2021-01-03 14:25:43 +05:30
- The pipeline has been [scheduled](../pipelines/schedules.md) **or** runs for `master`.
2020-05-24 23:13:21 +05:30
- The `variables` keyword matches.
- The `kubernetes` service is active on the project.
2018-04-04 21:44:52 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
script: npm run test
only:
refs:
- master
- schedules
variables:
- $CI_COMMIT_MESSAGE =~ /run-end-to-end-tests/
kubernetes: active
2018-04-04 21:44:52 +05:30
```
2020-11-24 15:15:51 +05:30
With `except`, individual keys are logically joined by an `OR`. A job is **not**
added if the following is true:
2018-04-04 21:44:52 +05:30
2020-11-24 15:15:51 +05:30
- `(any listed refs are true) OR (any listed variables are true) OR (any listed changes are true) OR (a chosen Kubernetes status matches)`
2018-10-15 14:42:47 +05:30
2021-01-03 14:25:43 +05:30
In the example below, the `test` job is **not** created when **any** of the following are true:
2018-04-04 21:44:52 +05:30
2020-11-24 15:15:51 +05:30
- The pipeline runs for the `master` branch.
2020-05-24 23:13:21 +05:30
- There are changes to the `README.md` file in the root directory of the repository.
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
```yaml
test:
script: npm run test
except:
refs:
- master
changes:
- "README.md"
```
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
#### `only:refs`/`except:refs`
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
> `refs` policy introduced in GitLab 10.0.
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
The `refs` strategy can take the same values as the
[simplified only/except configuration](#onlyexcept-basic).
2018-04-04 21:44:52 +05:30
2021-01-03 14:25:43 +05:30
In the example below, the `deploy` job is created only when the
pipeline is [scheduled](../pipelines/schedules.md) or runs for the `master` branch:
2018-04-04 21:44:52 +05:30
```yaml
2020-05-24 23:13:21 +05:30
deploy:
only:
refs:
- master
- schedules
2018-04-04 21:44:52 +05:30
```
2020-05-24 23:13:21 +05:30
#### `only:kubernetes`/`except:kubernetes`
> `kubernetes` policy introduced in GitLab 10.0.
The `kubernetes` strategy accepts only the `active` keyword.
2021-01-03 14:25:43 +05:30
In the example below, the `deploy` job is created only when the
2020-05-24 23:13:21 +05:30
Kubernetes service is active in the project:
2018-04-04 21:44:52 +05:30
```yaml
2020-05-24 23:13:21 +05:30
deploy:
only:
kubernetes: active
2018-04-04 21:44:52 +05:30
```
2020-05-24 23:13:21 +05:30
#### `only:variables`/`except:variables`
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
> `variables` policy introduced in GitLab 10.7.
2019-12-26 22:10:19 +05:30
2021-01-03 14:25:43 +05:30
The `variables` keyword defines variable expressions.
These expressions determine whether or not a job should be created.
2019-12-26 22:10:19 +05:30
2021-01-03 14:25:43 +05:30
Examples of using variable expressions:
2019-12-26 22:10:19 +05:30
```yaml
2020-05-24 23:13:21 +05:30
deploy:
script: cap staging deploy
only:
refs:
- branches
variables:
- $RELEASE == "staging"
- $STAGING
2019-12-26 22:10:19 +05:30
```
2020-05-24 23:13:21 +05:30
Another use case is excluding jobs depending on a commit message:
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
```yaml
end-to-end:
script: rake test:end-to-end
except:
variables:
- $CI_COMMIT_MESSAGE =~ /skip-end-to-end-tests/
```
2019-12-26 22:10:19 +05:30
2020-10-24 23:57:45 +05:30
You can use [parentheses](../variables/README.md#parentheses) with `&&` and `||` to build more complicated variable expressions.
[Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230938) in GitLab 13.3:
```yaml
job1:
script:
- echo This rule uses parentheses.
only:
variables:
- ($CI_COMMIT_BRANCH == "master" || $CI_COMMIT_BRANCH == "develop") && $MY_VARIABLE
```
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
#### `only:changes`/`except:changes`
2019-12-26 22:10:19 +05:30
2020-06-23 00:09:42 +05:30
> `changes` policy [introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/19232) in GitLab 11.4.
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
Using the `changes` keyword with `only` or `except` makes it possible to define if
a job should be created based on files modified by a Git push event.
2020-11-24 15:15:51 +05:30
The `only:changes` policy is only useful for pipelines triggered by the following
refs:
2020-05-24 23:13:21 +05:30
2020-11-24 15:15:51 +05:30
- `branches`
- `external_pull_requests`
- `merge_requests` (see additional details about [using `only:changes` with pipelines for merge requests](#using-onlychanges-with-pipelines-for-merge-requests))
2020-05-24 23:13:21 +05:30
2020-11-24 15:15:51 +05:30
CAUTION: **Caution:**
In pipelines with [sources other than the three above](../variables/predefined_variables.md)
`changes` can't determine if a given file is new or old and always returns `true`.
This includes pipelines triggered by pushing new tags. Configuring jobs to use `only: changes`
with other `only: refs` keywords is possible, but not recommended.
2020-05-24 23:13:21 +05:30
A basic example of using `only: changes`:
2019-12-26 22:10:19 +05:30
```yaml
2020-05-24 23:13:21 +05:30
docker build:
script: docker build -t my-image:$CI_COMMIT_REF_SLUG .
only:
2020-11-24 15:15:51 +05:30
refs:
- branches
2020-05-24 23:13:21 +05:30
changes:
- Dockerfile
- docker/scripts/*
- dockerfiles/**/*
- more_scripts/*.{rb,py,sh}
2019-12-26 22:10:19 +05:30
```
2021-01-03 14:25:43 +05:30
When you push commits to an existing branch,
the `docker build` job is created, but only if changes were made to any of the following:
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
- The `Dockerfile` file.
2021-01-03 14:25:43 +05:30
- Any of the files in the `docker/scripts/` directory.
- Any of the files and subdirectories in the `dockerfiles` directory.
- Any of the files with `rb`, `py`, `sh` extensions in the `more_scripts` directory.
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
CAUTION: **Warning:**
2021-01-03 14:25:43 +05:30
If you use `only:changes` with [only allow merge requests to be merged if the pipeline succeeds](../../user/project/merge_requests/merge_when_pipeline_succeeds.md#only-allow-merge-requests-to-be-merged-if-the-pipeline-succeeds),
you should [also use `only:merge_requests`](#using-onlychanges-with-pipelines-for-merge-requests). Otherwise it may not work as expected.
2020-05-24 23:13:21 +05:30
You can also use glob patterns to match multiple files in either the root directory
2021-01-03 14:25:43 +05:30
of the repository, or in _any_ directory within the repository. However, they must be wrapped
in double quotes or GitLab can't parse them. For example:
2018-04-04 21:44:52 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
script: npm run test
only:
2020-11-24 15:15:51 +05:30
refs:
- branches
2020-05-24 23:13:21 +05:30
changes:
- "*.json"
- "**/*.sql"
2018-04-04 21:44:52 +05:30
```
2021-01-03 14:25:43 +05:30
You can skip a job if a change is detected in any file with a
`.md` extension in the root directory of the repository:
2018-04-04 21:44:52 +05:30
```yaml
2020-05-24 23:13:21 +05:30
build:
script: npm run build
except:
changes:
- "*.md"
2018-04-04 21:44:52 +05:30
```
2021-01-03 14:25:43 +05:30
If you change multiple files, but only one file ends in `.md`,
the `build` job is still skipped. The job does not run for any of the files.
2018-04-04 21:44:52 +05:30
2021-01-03 14:25:43 +05:30
Read more about how to use this feature with:
- [New branches or tags *without* pipelines for merge requests](#using-onlychanges-without-pipelines-for-merge-requests).
- [Scheduled pipelines](#using-onlychanges-with-scheduled-pipelines).
2018-04-04 21:44:52 +05:30
2020-05-24 23:13:21 +05:30
##### Using `only:changes` with pipelines for merge requests
2020-05-24 23:13:21 +05:30
With [pipelines for merge requests](../merge_request_pipelines/index.md),
it's possible to define a job to be created based on files modified
in a merge request.
2016-09-29 09:46:39 +05:30
2021-01-03 14:25:43 +05:30
To deduce the correct base SHA of the source branch, we recommend combining
2020-05-24 23:13:21 +05:30
this keyword with `only: [merge_requests]`. This way, file differences are correctly
calculated from any further commits, thus all changes in the merge requests are properly
tested in pipelines.
2016-09-29 09:46:39 +05:30
2020-05-24 23:13:21 +05:30
For example:
2016-09-29 09:46:39 +05:30
2020-05-24 23:13:21 +05:30
```yaml
docker build service one:
script: docker build -t my-service-one-image:$CI_COMMIT_REF_SLUG .
only:
refs:
- merge_requests
changes:
- Dockerfile
- service-one/**/*
2016-09-29 09:46:39 +05:30
```
2021-01-03 14:25:43 +05:30
In this scenario, if a merge request changes
files in the `service-one` directory or the `Dockerfile`, GitLab creates
the `docker build service one` job.
2016-09-29 09:46:39 +05:30
2020-05-24 23:13:21 +05:30
For example:
2015-11-26 14:37:03 +05:30
2020-05-24 23:13:21 +05:30
```yaml
docker build service one:
script: docker build -t my-service-one-image:$CI_COMMIT_REF_SLUG .
only:
changes:
- Dockerfile
- service-one/**/*
```
2015-12-23 02:04:40 +05:30
2021-01-03 14:25:43 +05:30
In the example above, the pipeline might fail because of changes to a file in `service-one/**/*`.
A later commit that doesn't have changes in `service-one/**/*`
but does have changes to the `Dockerfile` can pass. The job
only tests the changes to the `Dockerfile`.
2015-12-23 02:04:40 +05:30
2021-01-03 14:25:43 +05:30
GitLab checks the **most recent pipeline** that **passed**. If the merge request is mergeable,
it doesn't matter that an earlier pipeline failed because of a change that has not been corrected.
When you use this configuration, ensure that the most recent pipeline
properly corrects any failures from previous pipelines.
2015-12-23 02:04:40 +05:30
2020-05-24 23:13:21 +05:30
##### Using `only:changes` without pipelines for merge requests
2015-11-26 14:37:03 +05:30
2020-05-24 23:13:21 +05:30
Without [pipelines for merge requests](../merge_request_pipelines/index.md), pipelines
run on branches or tags that don't have an explicit association with a merge request.
2020-10-24 23:57:45 +05:30
In this case, a previous SHA is used to calculate the diff, which is equivalent to `git diff HEAD~`.
This can result in some unexpected behavior, including:
2015-12-23 02:04:40 +05:30
2020-05-24 23:13:21 +05:30
- When pushing a new branch or a new tag to GitLab, the policy always evaluates to true.
- When pushing a new commit, the changed files are calculated using the previous commit
as the base SHA.
2019-09-30 21:07:59 +05:30
2020-05-24 23:13:21 +05:30
##### Using `only:changes` with scheduled pipelines
2015-11-26 14:37:03 +05:30
2020-05-24 23:13:21 +05:30
`only:changes` always evaluates as "true" in [Scheduled pipelines](../pipelines/schedules.md).
All files are considered to have "changed" when a scheduled pipeline
runs.
2015-12-23 02:04:40 +05:30
2020-05-24 23:13:21 +05:30
### `needs`
2015-11-26 14:37:03 +05:30
2020-06-23 00:09:42 +05:30
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/47063) in GitLab 12.2.
2020-05-24 23:13:21 +05:30
> - In GitLab 12.3, maximum number of jobs in `needs` array raised from five to 50.
2020-06-23 00:09:42 +05:30
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/30631) in GitLab 12.8, `needs: []` lets jobs start immediately.
2020-05-24 23:13:21 +05:30
The `needs:` keyword enables executing jobs out-of-order, allowing you to implement
a [directed acyclic graph](../directed_acyclic_graph/index.md) in your `.gitlab-ci.yml`.
This lets you run some jobs without waiting for other ones, disregarding stage ordering
so you can have multiple stages running concurrently.
Let's consider the following example:
2017-08-17 22:00:37 +05:30
```yaml
2020-05-24 23:13:21 +05:30
linux:build:
2017-08-17 22:00:37 +05:30
stage: build
2020-05-24 23:13:21 +05:30
mac:build:
stage: build
2016-04-02 18:10:28 +05:30
2020-05-24 23:13:21 +05:30
lint:
stage: test
needs: []
2016-04-02 18:10:28 +05:30
2020-05-24 23:13:21 +05:30
linux:rspec:
stage: test
needs: ["linux:build"]
2016-04-02 18:10:28 +05:30
2020-05-24 23:13:21 +05:30
linux:rubocop:
stage: test
needs: ["linux:build"]
2016-04-02 18:10:28 +05:30
2020-05-24 23:13:21 +05:30
mac:rspec:
stage: test
needs: ["mac:build"]
2020-04-22 19:07:51 +05:30
2020-05-24 23:13:21 +05:30
mac:rubocop:
stage: test
needs: ["mac:build"]
production:
stage: deploy
2020-04-22 19:07:51 +05:30
```
2020-05-24 23:13:21 +05:30
This example creates four paths of execution:
2019-12-26 22:10:19 +05:30
2021-01-03 14:25:43 +05:30
- Linter: the `lint` job runs immediately without waiting for the `build` stage to complete because it has no needs (`needs: []`).
2019-12-26 22:10:19 +05:30
2021-01-03 14:25:43 +05:30
- Linux path: the `linux:rspec` and `linux:rubocop` jobs runs as soon
2020-05-24 23:13:21 +05:30
as the `linux:build` job finishes without waiting for `mac:build` to finish.
2019-12-26 22:10:19 +05:30
2021-01-03 14:25:43 +05:30
- macOS path: the `mac:rspec` and `mac:rubocop` jobs runs as soon
2020-05-24 23:13:21 +05:30
as the `mac:build` job finishes, without waiting for `linux:build` to finish.
2021-01-03 14:25:43 +05:30
- The `production` job runs as soon as all previous jobs
2020-05-24 23:13:21 +05:30
finish; in this case: `linux:build`, `linux:rspec`, `linux:rubocop`,
`mac:build`, `mac:rspec`, `mac:rubocop`.
#### Requirements and limitations
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
- If `needs:` is set to point to a job that is not instantiated
because of `only/except` rules or otherwise does not exist, the
2021-01-03 14:25:43 +05:30
pipeline is not created and a YAML error is shown.
2020-05-24 23:13:21 +05:30
- The maximum number of jobs that a single job can need in the `needs:` array is limited:
2020-11-24 15:15:51 +05:30
- For GitLab.com, the limit is 50. For more information, see our
2020-06-23 00:09:42 +05:30
[infrastructure issue](https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/7541).
2020-11-24 15:15:51 +05:30
- For self-managed instances, the limit is: 50. This limit [can be changed](#changing-the-needs-job-limit).
2020-05-24 23:13:21 +05:30
- If `needs:` refers to a job that is marked as `parallel:`.
2021-01-03 14:25:43 +05:30
the current job depends on all parallel jobs being created.
- `needs:` is similar to `dependencies:` in that it must use jobs from prior stages,
2020-05-24 23:13:21 +05:30
meaning it's impossible to create circular dependencies. Depending on jobs in the
2020-06-23 00:09:42 +05:30
current stage is not possible either, but support [is planned](https://gitlab.com/gitlab-org/gitlab/-/issues/30632).
2020-05-24 23:13:21 +05:30
- Related to the above, stages must be explicitly defined for all jobs
that have the keyword `needs:` or are referred to by one.
2019-12-26 22:10:19 +05:30
2020-10-24 23:57:45 +05:30
##### Changing the `needs:` job limit **(CORE ONLY)**
2019-12-26 22:10:19 +05:30
2020-10-24 23:57:45 +05:30
The maximum number of jobs that can be defined within `needs:` defaults to 50.
2019-12-26 22:10:19 +05:30
2020-10-24 23:57:45 +05:30
A GitLab administrator with [access to the GitLab Rails console](../../administration/feature_flags.md)
can choose a custom limit. For example, to set the limit to 100:
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
```ruby
2020-10-24 23:57:45 +05:30
Plan.default.actual_limits.update!(ci_needs_size_limit: 100)
2020-05-24 23:13:21 +05:30
```
2015-11-26 14:37:03 +05:30
2021-01-03 14:25:43 +05:30
To disable directed acyclic graphs (DAG), set the limit to `0`.
2020-10-24 23:57:45 +05:30
2020-05-24 23:13:21 +05:30
#### Artifact downloads with `needs`
2015-12-23 02:04:40 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14311) in GitLab v12.6.
2015-12-23 02:04:40 +05:30
2020-07-28 23:09:34 +05:30
When using `needs`, artifact downloads are controlled with `artifacts: true` (default) or `artifacts: false`.
2021-01-03 14:25:43 +05:30
In GitLab 12.6 and later, you can't combine the [`dependencies`](#dependencies) keyword
2020-07-28 23:09:34 +05:30
with `needs` to control artifact downloads in jobs. `dependencies` is still valid
in jobs that do not use `needs`.
2018-11-08 19:23:39 +05:30
2021-01-03 14:25:43 +05:30
In the example below, the `rspec` job downloads the `build_job` artifacts, while the
`rubocop` job doesn't:
2015-12-23 02:04:40 +05:30
```yaml
2020-05-24 23:13:21 +05:30
build_job:
stage: build
2016-06-02 11:05:42 +05:30
artifacts:
2018-10-15 14:42:47 +05:30
paths:
2018-11-08 19:23:39 +05:30
- binaries/
2020-05-24 23:13:21 +05:30
rspec:
stage: test
needs:
- job: build_job
artifacts: true
rubocop:
stage: test
needs:
- job: build_job
artifacts: false
2015-11-26 14:37:03 +05:30
```
2021-01-03 14:25:43 +05:30
Additionally, in the three syntax examples below, the `rspec` job downloads the artifacts
from all three `build_jobs`. `artifacts` is true for `build_job_1` and
**defaults** to true for both `build_job_2` and `build_job_3`.
2015-12-23 02:04:40 +05:30
```yaml
2020-05-24 23:13:21 +05:30
rspec:
needs:
- job: build_job_1
artifacts: true
- job: build_job_2
- build_job_3
2016-06-02 11:05:42 +05:30
```
2020-05-24 23:13:21 +05:30
#### Cross project artifact downloads with `needs` **(PREMIUM)**
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14311) in GitLab v12.7.
2020-05-24 23:13:21 +05:30
2021-01-03 14:25:43 +05:30
Use `needs` to download artifacts from up to five jobs in pipelines:
- [On other refs in the same project](#artifact-downloads-between-pipelines-in-the-same-project).
- In different projects, groups and namespaces.
2016-06-02 11:05:42 +05:30
```yaml
2020-05-24 23:13:21 +05:30
build_job:
stage: build
script:
- ls -lhR
needs:
2020-10-24 23:57:45 +05:30
- project: namespace/group/project-name
2020-05-24 23:13:21 +05:30
job: build-1
ref: master
artifacts: true
2015-11-26 14:37:03 +05:30
```
2021-01-03 14:25:43 +05:30
`build_job` downloads the artifacts from the latest successful `build-1` job
2020-10-24 23:57:45 +05:30
on the `master` branch in the `group/project-name` project. If the project is in the
same group or namespace, you can omit them from the `project:` key. For example,
`project: group/project-name` or `project: project-name`.
The user running the pipeline must have at least `reporter` access to the group or project, or the group/project must have public visibility.
2020-05-24 23:13:21 +05:30
##### Artifact downloads between pipelines in the same project
2021-01-03 14:25:43 +05:30
Use `needs` to download artifacts from different pipelines in the current project.
Set the `project` keyword as the current project's name, and specify a ref.
In this example, `build_job` downloads the artifacts for the latest successful
2020-05-24 23:13:21 +05:30
`build-1` job with the `other-ref` ref:
2015-12-23 02:04:40 +05:30
```yaml
2020-05-24 23:13:21 +05:30
build_job:
stage: build
script:
- ls -lhR
needs:
- project: group/same-project-name
job: build-1
ref: other-ref
artifacts: true
2015-11-26 14:37:03 +05:30
```
2020-10-24 23:57:45 +05:30
Environment variables support for `project:`, `job:`, and `ref` was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/202093)
2020-11-24 15:15:51 +05:30
in GitLab 13.3. [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/235761) in GitLab 13.4.
2020-10-24 23:57:45 +05:30
For example:
```yaml
build_job:
stage: build
script:
- ls -lhR
needs:
- project: $CI_PROJECT_PATH
job: $DEPENDENCY_JOB_NAME
ref: $CI_COMMIT_BRANCH
artifacts: true
```
2020-05-24 23:13:21 +05:30
Downloading artifacts from jobs that are run in [`parallel:`](#parallel) is not supported.
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
### `tags`
2020-11-24 15:15:51 +05:30
Use `tags` to select a specific runner from the list of all runners that are
available for the project.
2020-05-24 23:13:21 +05:30
2020-11-24 15:15:51 +05:30
When you register a runner, you can specify the runner's tags, for
2020-05-24 23:13:21 +05:30
example `ruby`, `postgres`, `development`.
2020-11-24 15:15:51 +05:30
In this example, the job is run by a runner that
2021-01-03 14:25:43 +05:30
has both `ruby` and `postgres` tags defined.
2015-11-26 14:37:03 +05:30
2015-12-23 02:04:40 +05:30
```yaml
2016-06-02 11:05:42 +05:30
job:
2020-05-24 23:13:21 +05:30
tags:
- ruby
- postgres
2016-06-02 11:05:42 +05:30
```
2015-11-26 14:37:03 +05:30
2020-11-24 15:15:51 +05:30
You can use tags to run different jobs on different platforms. For
example, if you have an OS X runner with tag `osx` and a Windows runner with tag
`windows`, you can run a job on each platform:
2017-09-10 17:25:29 +05:30
```yaml
2020-05-24 23:13:21 +05:30
windows job:
stage:
- build
tags:
- windows
script:
- echo Hello, %USERNAME%!
osx job:
stage:
- build
tags:
- osx
script:
- echo "Hello, $USER!"
2018-10-15 14:42:47 +05:30
```
2020-05-24 23:13:21 +05:30
### `allow_failure`
2018-10-15 14:42:47 +05:30
2020-11-24 15:15:51 +05:30
Use `allow_failure` when you want to let a job fail without impacting the rest of the CI
2020-05-24 23:13:21 +05:30
suite.
The default value is `false`, except for [manual](#whenmanual) jobs using the
`when: manual` syntax, unless using [`rules:`](#rules) syntax, where all jobs
default to false, *including* `when: manual` jobs.
2018-10-15 14:42:47 +05:30
2021-01-03 14:25:43 +05:30
When `allow_failure` is enabled and the job fails, the job shows an orange warning in the UI.
However, the logical flow of the pipeline considers the job a
2020-05-24 23:13:21 +05:30
success/passed, and is not blocked.
2018-10-15 14:42:47 +05:30
2021-01-03 14:25:43 +05:30
Assuming all other jobs are successful, the job's stage and its pipeline
show the same orange warning. However, the associated commit is marked as
2020-05-24 23:13:21 +05:30
"passed", without warnings.
2021-01-03 14:25:43 +05:30
In the example below, `job1` and `job2` run in parallel, but if `job1`
fails, it doesn't stop the next stage from running, because it's marked with
2020-05-24 23:13:21 +05:30
`allow_failure: true`:
2018-10-15 14:42:47 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job1:
stage: test
script:
- execute_script_that_will_fail
allow_failure: true
2018-10-15 14:42:47 +05:30
2020-05-24 23:13:21 +05:30
job2:
stage: test
script:
- execute_script_that_will_succeed
2018-10-15 14:42:47 +05:30
2020-05-24 23:13:21 +05:30
job3:
stage: deploy
script:
- deploy_to_staging
2017-09-10 17:25:29 +05:30
```
2020-05-24 23:13:21 +05:30
### `when`
`when` is used to implement jobs that are run in case of failure or despite the
failure.
`when` can be set to one of the following values:
1. `on_success` - execute job only when all jobs from prior stages
2021-01-03 14:25:43 +05:30
succeed (or are considered succeeding because they have `allow_failure: true`).
This is the default.
2020-05-24 23:13:21 +05:30
1. `on_failure` - execute job only when at least one job from prior stages
fails.
1. `always` - execute job regardless of the status of jobs from prior stages.
1. `manual` - execute job manually (added in GitLab 8.10). Read about
2021-01-03 14:25:43 +05:30
[manual jobs](#whenmanual) below.
2020-05-24 23:13:21 +05:30
1. `delayed` - execute job after a certain period (added in GitLab 11.14).
2021-01-03 14:25:43 +05:30
Read about [delayed jobs](#whendelayed) below.
2020-10-24 23:57:45 +05:30
1. `never`:
- With [`rules`](#rules), don't execute job.
- With [`workflow:rules`](#workflowrules), don't run pipeline.
2020-05-24 23:13:21 +05:30
For example:
2020-05-24 23:13:21 +05:30
```yaml
stages:
- build
- cleanup_build
- test
- deploy
- cleanup
2020-05-24 23:13:21 +05:30
build_job:
stage: build
script:
- make build
2020-05-24 23:13:21 +05:30
cleanup_build_job:
stage: cleanup_build
script:
- cleanup build when failed
when: on_failure
2020-05-24 23:13:21 +05:30
test_job:
stage: test
script:
- make test
2020-05-24 23:13:21 +05:30
deploy_job:
stage: deploy
script:
- make deploy
when: manual
2020-05-24 23:13:21 +05:30
cleanup_job:
stage: cleanup
script:
- cleanup after jobs
when: always
```
2020-11-24 15:15:51 +05:30
The above script:
2020-11-24 15:15:51 +05:30
1. Executes `cleanup_build_job` only when `build_job` fails.
1. Always executes `cleanup_job` as the last step in pipeline regardless of
2020-05-24 23:13:21 +05:30
success or failure.
2020-11-24 15:15:51 +05:30
1. Executes `deploy_job` when you run it manually in the GitLab UI.
2020-05-24 23:13:21 +05:30
#### `when:manual`
2020-05-24 23:13:21 +05:30
> - Introduced in GitLab 8.10.
2021-01-03 14:25:43 +05:30
> - Blocking manual jobs were introduced in GitLab 9.0.
2020-05-24 23:13:21 +05:30
> - Protected actions were introduced in GitLab 9.2.
2021-01-03 14:25:43 +05:30
A manual job is a type of job that is not executed automatically and must be explicitly
started by a user. You might want to use manual jobs for things like deploying to production.
2021-01-03 14:25:43 +05:30
To make a job manual, add `when: manual` to its configuration.
2017-08-17 22:00:37 +05:30
2021-01-03 14:25:43 +05:30
Manual jobs can be started from the pipeline, job, [environment](../environments/index.md#configuring-manual-deployments),
and deployment views.
2021-01-03 14:25:43 +05:30
Manual jobs can be either optional or blocking:
2021-01-03 14:25:43 +05:30
- **Optional**: Manual jobs have [`allow_failure: true](#allow_failure) set by default
and are considered optional. The status of an optional manual job does not contribute
to the overall pipeline status. A pipeline can succeed even if all its manual jobs fail.
2021-01-03 14:25:43 +05:30
- **Blocking**: To make a blocking manual job, add `allow_failure: false` to its configuration.
Blocking manual jobs stop further execution of the pipeline at the stage where the
job is defined. To let the pipeline continue running, click **{play}** (play) on
the blocking manual job.
2018-11-18 11:00:15 +05:30
2021-01-03 14:25:43 +05:30
Merge requests in projects with [merge when pipeline succeeds](../../user/project/merge_requests/merge_when_pipeline_succeeds.md)
enabled can't be merged with a blocked pipeline. Blocked pipelines show a status
of **blocked**.
When you use [`rules:`](#rules), `allow_failure` defaults to `false`, including for manual jobs.
To trigger a manual job, a user must have permission to merge to the assigned branch.
You can use [protected branches](../../user/project/protected_branches.md) to more strictly
[protect manual deployments](#protecting-manual-jobs) from being run by unauthorized users.
In [GitLab 13.5](https://gitlab.com/gitlab-org/gitlab/-/issues/201938) and later, you
can use `when:manual` in the same job as [`trigger`](#trigger). In GitLab 13.4 and
earlier, using them together causes the error `jobs:#{job-name} when should be on_success, on_failure or always`.
It is deployed behind the `:ci_manual_bridges` [feature flag](../../user/feature_flags.md), which is **enabled by default**.
[GitLab administrators with access to the Rails console](../../administration/feature_flags.md)
can opt to disable it.
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
##### Protecting manual jobs **(PREMIUM)**
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
It's possible to use [protected environments](../environments/protected_environments.md)
to define a precise list of users authorized to run a manual job. By allowing only
users associated with a protected environment to trigger manual jobs, it's possible
to implement some special use cases, such as:
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
- More precisely limiting who can deploy to an environment.
- Enabling a pipeline to be blocked until an approved user "approves" it.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
To do this, you must:
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
1. Add an `environment` to the job. For example:
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
```yaml
deploy_prod:
stage: deploy
script:
- echo "Deploy to production server"
environment:
name: production
url: https://example.com
when: manual
only:
- master
```
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
1. In the [protected environments settings](../environments/protected_environments.md#protecting-environments),
select the environment (`production` in the example above) and add the users, roles or groups
that are authorized to trigger the manual job to the **Allowed to Deploy** list. Only those in
2021-01-03 14:25:43 +05:30
this list can trigger this manual job, as well as GitLab administrators
2020-05-24 23:13:21 +05:30
who are always able to use protected environments.
2018-11-18 11:00:15 +05:30
2021-01-03 14:25:43 +05:30
Additionally, if you define a manual job as blocking by adding `allow_failure: false`,
the pipeline's next stages don't run until the manual job is triggered. You can use this
to define a list of users allowed to "approve" later pipeline
2020-05-24 23:13:21 +05:30
stages by triggering the blocking manual job.
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
#### `when:delayed`
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/51352) in GitLab 11.4.
2018-11-18 11:00:15 +05:30
2020-05-24 23:13:21 +05:30
Delayed job are for executing scripts after a certain period.
This is useful if you want to avoid jobs entering `pending` state immediately.
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
You can set the period with `start_in` key. The value of `start_in` key is an elapsed time in seconds, unless a unit is
provided. `start_in` key must be less than or equal to one week. Examples of valid values include:
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
- `'5'`
2020-11-24 15:15:51 +05:30
- `5 seconds`
2020-05-24 23:13:21 +05:30
- `30 minutes`
- `1 day`
- `1 week`
2020-04-08 14:13:33 +05:30
2021-01-03 14:25:43 +05:30
When there is a delayed job in a stage, the pipeline doesn't progress until the delayed job has finished.
2020-05-24 23:13:21 +05:30
This means this keyword can also be used for inserting delays between different stages.
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
The timer of a delayed job starts immediately after the previous stage has completed.
2021-01-03 14:25:43 +05:30
Similar to other types of jobs, a delayed job's timer doesn't start unless the previous stage passed.
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
The following example creates a job named `timed rollout 10%` that is executed 30 minutes after the previous stage has completed:
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
```yaml
timed rollout 10%:
stage: deploy
script: echo 'Rolling out 10% ...'
when: delayed
start_in: 30 minutes
```
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
You can stop the active timer of a delayed job by clicking the **{time-out}** (**Unschedule**) button.
2021-01-03 14:25:43 +05:30
This job can no longer be scheduled to run automatically. You can, however, execute the job manually.
2020-04-08 14:13:33 +05:30
2020-10-24 23:57:45 +05:30
To start a delayed job immediately, click the **Play** button.
Soon GitLab Runner picks up and starts the job.
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
### `environment`
2020-04-08 14:13:33 +05:30
2020-05-24 23:13:21 +05:30
> - Introduced in GitLab 8.9.
> - You can read more about environments and find more examples in the
> [documentation about environments](../environments/index.md).
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
`environment` is used to define that a job deploys to a specific environment.
If `environment` is specified and no environment under that name exists, a new
2021-01-03 14:25:43 +05:30
one is created automatically.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
In its simplest form, the `environment` keyword can be defined like:
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
```yaml
deploy to production:
stage: deploy
script: git push production HEAD:master
environment: production
```
2018-12-13 13:39:08 +05:30
2021-01-03 14:25:43 +05:30
In the above example, the `deploy to production` job is marked as doing a
2020-05-24 23:13:21 +05:30
deployment to the `production` environment.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
#### `environment:name`
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
> - Introduced in GitLab 8.11.
> - Before GitLab 8.11, the name of an environment could be defined as a string like
> `environment: production`. The recommended way now is to define it under the
> `name` keyword.
> - The `name` parameter can use any of the defined CI variables,
> including predefined, secure variables and `.gitlab-ci.yml` [`variables`](#variables).
> You however can't use variables defined under `script`.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
The `environment` name can contain:
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
- letters
- digits
- spaces
- `-`
- `_`
- `/`
- `$`
- `{`
- `}`
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
Common names are `qa`, `staging`, and `production`, but you can use whatever
name works with your workflow.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
Instead of defining the name of the environment right after the `environment`
keyword, it's also possible to define it as a separate value. For that, use
the `name` keyword under `environment`:
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
```yaml
deploy to production:
stage: deploy
script: git push production HEAD:master
environment:
name: production
```
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
#### `environment:url`
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
> - Introduced in GitLab 8.11.
> - Before GitLab 8.11, the URL could be added only in GitLab's UI. The
> recommended way now is to define it in `.gitlab-ci.yml`.
> - The `url` parameter can use any of the defined CI variables,
> including predefined, secure variables and `.gitlab-ci.yml` [`variables`](#variables).
> You however can't use variables defined under `script`.
2018-12-13 13:39:08 +05:30
2020-10-24 23:57:45 +05:30
This optional value exposes buttons that take you to the defined URL
2018-12-13 13:39:08 +05:30
2020-10-24 23:57:45 +05:30
In this example, if the job finishes successfully, it creates buttons
in the merge requests and in the environments/deployments pages that point
2020-05-24 23:13:21 +05:30
to `https://prod.example.com`.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
```yaml
deploy to production:
stage: deploy
script: git push production HEAD:master
environment:
name: production
url: https://prod.example.com
```
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
#### `environment:on_stop`
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/22191) in GitLab 8.13.
> - Starting with GitLab 8.14, when you have an environment that has a stop action
2021-01-03 14:25:43 +05:30
> defined, GitLab automatically triggers a stop action when the associated
2020-05-24 23:13:21 +05:30
> branch is deleted.
2018-12-13 13:39:08 +05:30
2021-01-03 14:25:43 +05:30
Closing (stopping) environments can be achieved with the `on_stop` keyword
defined under `environment`. It declares a different job that runs to close the
environment.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
Read the `environment:action` section for an example.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
#### `environment:action`
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/22191) in GitLab 8.13.
2018-12-13 13:39:08 +05:30
2020-10-24 23:57:45 +05:30
The `action` keyword can be used to specify jobs that prepare, start, or stop environments.
| **Value** | **Description** |
|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
2021-01-03 14:25:43 +05:30
| start | Default value. Indicates that job starts the environment. The deployment is created after the job starts. |
2020-10-24 23:57:45 +05:30
| prepare | Indicates that job is only preparing the environment. Does not affect deployments. [Read more about environments](../environments/index.md#prepare-an-environment) |
| stop | Indicates that job stops deployment. See the example below. |
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
Take for instance:
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
```yaml
review_app:
stage: deploy
script: make deploy-app
environment:
2020-07-28 23:09:34 +05:30
name: review/$CI_COMMIT_REF_NAME
url: https://$CI_ENVIRONMENT_SLUG.example.com
2020-05-24 23:13:21 +05:30
on_stop: stop_review_app
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
stop_review_app:
stage: deploy
variables:
GIT_STRATEGY: none
script: make delete-app
when: manual
environment:
2020-07-28 23:09:34 +05:30
name: review/$CI_COMMIT_REF_NAME
2020-05-24 23:13:21 +05:30
action: stop
```
2020-03-13 15:44:24 +05:30
2021-01-03 14:25:43 +05:30
In the above example, the `review_app` job deploys to the `review`
environment. A new `stop_review_app` job is listed under `on_stop`.
After the `review_app` job is finished, it triggers the
`stop_review_app` job based on what is defined under `when`. In this case,
it is set to `manual`, so it needs a [manual action](#whenmanual) from
GitLab's user interface to run.
2020-03-13 15:44:24 +05:30
2021-01-03 14:25:43 +05:30
Also in the example, `GIT_STRATEGY` is set to `none`. If the
`stop_review_app` job is [automatically triggered](../environments/index.md#automatically-stopping-an-environment),
the runner wont try to check out the code after the branch is deleted.
2018-12-13 13:39:08 +05:30
2021-01-03 14:25:43 +05:30
The example also overwrites global variables. If your `stop` `environment` job depends
on global variables, you can use [anchor variables](#yaml-anchors-for-variables) when you set the `GIT_STRATEGY`.
This changes the job without overriding the global variables.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
The `stop_review_app` job is **required** to have the following keywords defined:
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
- `when` - [reference](#when)
- `environment:name`
- `environment:action`
2018-12-13 13:39:08 +05:30
2020-06-23 00:09:42 +05:30
Additionally, both jobs should have matching [`rules`](../yaml/README.md#onlyexcept-basic)
2021-01-03 14:25:43 +05:30
or [`only/except`](../yaml/README.md#onlyexcept-basic) configuration.
In the example above, if the configuration is not identical:
- The `stop_review_app` job might not be included in all pipelines that include the `review_app` job.
- It is not possible to trigger the `action: stop` to stop the environment automatically.
2020-06-23 00:09:42 +05:30
2020-05-24 23:13:21 +05:30
#### `environment:auto_stop_in`
2018-12-13 13:39:08 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/20956) in GitLab 12.8.
2019-07-31 22:56:46 +05:30
2020-05-24 23:13:21 +05:30
The `auto_stop_in` keyword is for specifying life period of the environment,
that when expired, GitLab automatically stops them.
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
For example,
2019-07-31 22:56:46 +05:30
2020-05-24 23:13:21 +05:30
```yaml
review_app:
script: deploy-review-app
environment:
name: review/$CI_COMMIT_REF_NAME
auto_stop_in: 1 day
```
2019-07-31 22:56:46 +05:30
2020-05-24 23:13:21 +05:30
When `review_app` job is executed and a review app is created, a life period of
the environment is set to `1 day`.
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
For more information, see
[the environments auto-stop documentation](../environments/index.md#environments-auto-stop)
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
#### `environment:kubernetes`
2016-06-02 11:05:42 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/27630) in GitLab 12.6.
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
The `kubernetes` block is used to configure deployments to a
[Kubernetes cluster](../../user/project/clusters/index.md) that is associated with your project.
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
For example:
2016-06-02 11:05:42 +05:30
```yaml
deploy:
stage: deploy
2020-05-24 23:13:21 +05:30
script: make deploy-app
environment:
name: production
kubernetes:
namespace: production
2015-11-26 14:37:03 +05:30
```
2021-01-03 14:25:43 +05:30
This configuration sets up the `deploy` job to deploy to the `production`
2020-05-24 23:13:21 +05:30
environment, using the `production`
[Kubernetes namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).
2018-03-17 18:26:18 +05:30
2020-05-24 23:13:21 +05:30
For more information, see
[Available settings for `kubernetes`](../environments/index.md#configuring-kubernetes-deployments).
2018-03-17 18:26:18 +05:30
NOTE: **Note:**
2020-05-24 23:13:21 +05:30
Kubernetes configuration is not supported for Kubernetes clusters
that are [managed by GitLab](../../user/project/clusters/index.md#gitlab-managed-clusters).
To follow progress on support for GitLab-managed clusters, see the
2020-06-23 00:09:42 +05:30
[relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/38054).
2019-10-12 21:52:04 +05:30
2020-05-24 23:13:21 +05:30
#### Dynamic environments
2019-10-12 21:52:04 +05:30
2020-05-24 23:13:21 +05:30
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/21971) in GitLab 8.12 and GitLab Runner 1.6.
> - The `$CI_ENVIRONMENT_SLUG` was [introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/22864) in GitLab 8.15.
> - The `name` and `url` parameters can use any of the defined CI variables,
> including predefined, secure variables and `.gitlab-ci.yml` [`variables`](#variables).
> You however can't use variables defined under `script`.
2019-10-12 21:52:04 +05:30
2020-05-24 23:13:21 +05:30
For example:
2019-10-12 21:52:04 +05:30
```yaml
2020-05-24 23:13:21 +05:30
deploy as review app:
2019-10-12 21:52:04 +05:30
stage: deploy
2020-05-24 23:13:21 +05:30
script: make deploy
environment:
name: review/$CI_COMMIT_REF_NAME
url: https://$CI_ENVIRONMENT_SLUG.example.com/
2019-10-12 21:52:04 +05:30
```
2021-01-03 14:25:43 +05:30
The `deploy as review app` job is marked as deployment to dynamically
2020-05-24 23:13:21 +05:30
create the `review/$CI_COMMIT_REF_NAME` environment, where `$CI_COMMIT_REF_NAME`
2020-10-24 23:57:45 +05:30
is an [environment variable](../variables/README.md) set by the runner. The
2020-05-24 23:13:21 +05:30
`$CI_ENVIRONMENT_SLUG` variable is based on the environment name, but suitable
2021-01-03 14:25:43 +05:30
for inclusion in URLs. In this case, if the `deploy as review app` job is run
2020-05-24 23:13:21 +05:30
in a branch named `pow`, this environment would be accessible with an URL like
`https://review-pow.example.com/`.
2019-10-12 21:52:04 +05:30
2020-10-24 23:57:45 +05:30
This implies that the underlying server that hosts the application
2020-05-24 23:13:21 +05:30
is properly configured.
2019-10-12 21:52:04 +05:30
2020-05-24 23:13:21 +05:30
The common use case is to create dynamic environments for branches and use them
as Review Apps. You can see a simple example using Review Apps at
<https://gitlab.com/gitlab-examples/review-apps-nginx/>.
2019-10-12 21:52:04 +05:30
2020-05-24 23:13:21 +05:30
### `cache`
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
> - Introduced in GitLab Runner v0.7.0.
> - `cache` can be set globally and per-job.
> - From GitLab 9.0, caching is enabled and shared between pipelines and jobs
> by default.
> - From GitLab 9.2, caches are restored before [artifacts](#artifacts).
2020-03-13 15:44:24 +05:30
2020-10-24 23:57:45 +05:30
`cache` is used to specify a list of files and directories that should be
2020-05-24 23:13:21 +05:30
cached between jobs. You can only use paths that are within the local working
copy.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
If `cache` is defined outside the scope of jobs, it means it's set
2021-01-03 14:25:43 +05:30
globally and all jobs use that definition.
Read how caching works and find out some good practices in the
[caching dependencies documentation](../caching/index.md).
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
#### `cache:paths`
2020-01-01 13:55:28 +05:30
2020-10-24 23:57:45 +05:30
Use the `paths` directive to choose which files or directories to cache. Paths
2020-05-24 23:13:21 +05:30
are relative to the project directory (`$CI_PROJECT_DIR`) and can't directly link outside it.
Wildcards can be used that follow the [glob](https://en.wikipedia.org/wiki/Glob_(programming))
patterns and:
2020-01-01 13:55:28 +05:30
2020-05-24 23:13:21 +05:30
- In [GitLab Runner 13.0](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2620) and later,
[`doublestar.Glob`](https://pkg.go.dev/github.com/bmatcuk/doublestar@v1.2.2?tab=doc#Match).
- In GitLab Runner 12.10 and earlier,
[`filepath.Match`](https://pkg.go.dev/path/filepath/#Match).
2020-01-01 13:55:28 +05:30
2020-05-24 23:13:21 +05:30
Cache all files in `binaries` that end in `.apk` and the `.config` file:
2020-01-01 13:55:28 +05:30
```yaml
rspec:
2020-05-24 23:13:21 +05:30
script: test
cache:
paths:
- binaries/*.apk
- .config
2020-01-01 13:55:28 +05:30
```
2020-05-24 23:13:21 +05:30
Locally defined cache overrides globally defined options. The following `rspec`
2021-01-03 14:25:43 +05:30
job caches only `binaries/`:
2020-01-01 13:55:28 +05:30
```yaml
2020-05-24 23:13:21 +05:30
cache:
paths:
- my/files
2020-01-01 13:55:28 +05:30
rspec:
2020-05-24 23:13:21 +05:30
script: test
cache:
key: rspec
paths:
- binaries/
2020-01-01 13:55:28 +05:30
```
2021-01-03 14:25:43 +05:30
The cache is shared between jobs, so if you're using different
paths for different jobs, you should also set a different `cache:key`.
Otherwise cache content can be overwritten.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
#### `cache:key`
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab Runner v1.0.0.
2020-03-13 15:44:24 +05:30
2021-01-03 14:25:43 +05:30
The cache is shared between jobs, so if you're using different
paths for different jobs, you should also set a different `cache:key`.
Otherwise cache content can be overwritten.
2020-03-13 15:44:24 +05:30
2021-01-03 14:25:43 +05:30
The `key` parameter defines the affinity of caching between jobs.
You can have a single cache for all jobs, cache per-job, cache per-branch,
2020-05-24 23:13:21 +05:30
or any other way that fits your workflow. This way, you can fine tune caching,
2020-11-24 15:15:51 +05:30
including caching data between different jobs or even different branches.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
The `cache:key` variable can use any of the
2020-10-24 23:57:45 +05:30
[predefined variables](../variables/README.md). The default key, if not
set, is just literal `default`, which means everything is shared between
2020-05-24 23:13:21 +05:30
pipelines and jobs by default, starting from GitLab 9.0.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
For example, to enable per-branch caching:
2020-03-13 15:44:24 +05:30
```yaml
2020-05-24 23:13:21 +05:30
cache:
key: "$CI_COMMIT_REF_SLUG"
paths:
- binaries/
2020-03-13 15:44:24 +05:30
```
2020-05-24 23:13:21 +05:30
If you use **Windows Batch** to run your shell scripts you need to replace
`$` with `%`:
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
```yaml
cache:
key: "%CI_COMMIT_REF_SLUG%"
paths:
- binaries/
```
2016-06-02 11:05:42 +05:30
2021-01-03 14:25:43 +05:30
The `cache:key` variable can't contain the `/` character, or the equivalent
URI-encoded `%2F`. A value made only of dots (`.`, `%2E`) is also forbidden.
You can specify a [fallback cache key](#fallback-cache-key) to use if the specified `cache:key` is not found.
2020-05-24 23:13:21 +05:30
##### `cache:key:files`
2017-08-17 22:00:37 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/18986) in GitLab v12.5.
2017-08-17 22:00:37 +05:30
2020-05-24 23:13:21 +05:30
The `cache:key:files` keyword extends the `cache:key` functionality by making it easier
2021-01-03 14:25:43 +05:30
to reuse some caches, and rebuild them less often, which speeds up subsequent pipeline
2020-05-24 23:13:21 +05:30
runs.
2017-08-17 22:00:37 +05:30
2021-01-03 14:25:43 +05:30
When you include `cache:key:files`, you must also list the project files that are used to generate the key, up to a maximum of two files.
The cache `key` is a SHA checksum computed from the most recent commits (up to two, if two files are listed)
2020-05-24 23:13:21 +05:30
that changed the given files. If neither file was changed in any commits,
2021-01-03 14:25:43 +05:30
the fallback key is `default`.
2017-08-17 22:00:37 +05:30
```yaml
2020-05-24 23:13:21 +05:30
cache:
key:
files:
- Gemfile.lock
- package.json
paths:
- vendor/ruby
- node_modules
2017-08-17 22:00:37 +05:30
```
2020-05-24 23:13:21 +05:30
In this example we're creating a cache for Ruby and Node.js dependencies that
is tied to current versions of the `Gemfile.lock` and `package.json` files. Whenever one of
these files changes, a new cache key is computed and a new cache is created. Any future
2021-01-03 14:25:43 +05:30
job runs that use the same `Gemfile.lock` and `package.json` with `cache:key:files`
2020-05-24 23:13:21 +05:30
use the new cache, instead of rebuilding the dependencies.
2017-09-10 17:25:29 +05:30
2020-05-24 23:13:21 +05:30
##### `cache:key:prefix`
2017-09-10 17:25:29 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/18986) in GitLab v12.5.
2017-09-10 17:25:29 +05:30
2020-11-24 15:15:51 +05:30
When you want to combine a prefix with the SHA computed for `cache:key:files`,
use the `prefix` parameter with `key:files`.
For example, if you add a `prefix` of `test`, the resulting key is: `test-feef9576d21ee9b6a32e30c5c79d0a0ceb68d1e5`.
2020-05-24 23:13:21 +05:30
If neither file was changed in any commits, the prefix is added to `default`, so the
key in the example would be `test-default`.
2017-09-10 17:25:29 +05:30
2020-05-24 23:13:21 +05:30
Like `cache:key`, `prefix` can use any of the [predefined variables](../variables/README.md),
but the following are not allowed:
2017-09-10 17:25:29 +05:30
2020-05-24 23:13:21 +05:30
- the `/` character (or the equivalent URI-encoded `%2F`)
- a value made only of `.` (or the equivalent URI-encoded `%2E`)
2017-09-10 17:25:29 +05:30
```yaml
2020-05-24 23:13:21 +05:30
cache:
key:
files:
- Gemfile.lock
prefix: ${CI_JOB_NAME}
paths:
- vendor/ruby
rspec:
script:
- bundle exec rspec
2017-09-10 17:25:29 +05:30
```
2021-01-03 14:25:43 +05:30
For example, adding a `prefix` of `$CI_JOB_NAME`
causes the key to look like: `rspec-feef9576d21ee9b6a32e30c5c79d0a0ceb68d1e5` and
2020-05-24 23:13:21 +05:30
the job cache is shared across different branches. If a branch changes
2021-01-03 14:25:43 +05:30
`Gemfile.lock`, that branch has a new SHA checksum for `cache:key:files`. A new cache key
is generated, and a new cache is created for that key.
2020-05-24 23:13:21 +05:30
If `Gemfile.lock` is not found, the prefix is added to
`default`, so the key in the example would be `rspec-default`.
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
#### `cache:untracked`
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
Set `untracked: true` to cache all files that are untracked in your Git
repository:
2018-12-13 13:39:08 +05:30
```yaml
2020-05-24 23:13:21 +05:30
rspec:
script: test
cache:
untracked: true
2018-12-13 13:39:08 +05:30
```
2020-05-24 23:13:21 +05:30
Cache all Git untracked files and files in `binaries`:
2018-12-13 13:39:08 +05:30
```yaml
2020-05-24 23:13:21 +05:30
rspec:
script: test
cache:
untracked: true
paths:
- binaries/
2018-12-13 13:39:08 +05:30
```
2021-01-03 14:25:43 +05:30
#### `cache:when`
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/18969) in GitLab 13.5 and GitLab Runner v13.5.0.
`cache:when` defines when to save the cache, based on the status of the job. You can
set `cache:when` to:
- `on_success` - save the cache only when the job succeeds. This is the default.
- `on_failure` - save the cache only when the job fails.
- `always` - save the cache regardless of the job status.
For example, to store a cache whether or not the job fails or succeeds:
```yaml
rspec:
script: rspec
cache:
paths:
- rspec/
when: 'always'
```
2020-05-24 23:13:21 +05:30
#### `cache:policy`
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 9.4.
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
The default behavior of a caching job is to download the files at the start of
2020-11-24 15:15:51 +05:30
execution, and to re-upload them at the end. Any changes made by the
job are persisted for future runs. This behavior is known as the `pull-push` cache
2020-05-24 23:13:21 +05:30
policy.
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
If you know the job does not alter the cached files, you can skip the upload step
by setting `policy: pull` in the job specification. Typically, this would be
twinned with an ordinary cache job at an earlier stage to ensure the cache
is updated from time to time:
2019-12-04 20:38:33 +05:30
```yaml
2020-05-24 23:13:21 +05:30
stages:
- setup
- test
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
prepare:
stage: setup
cache:
key: gems
paths:
- vendor/bundle
script:
- bundle install --deployment
rspec:
stage: test
cache:
key: gems
paths:
- vendor/bundle
policy: pull
script:
- bundle exec rspec ...
2019-12-04 20:38:33 +05:30
```
2021-01-03 14:25:43 +05:30
This helps to speed up job execution and reduce load on the cache server.
It is especially helpful when you have a large number of cache-using jobs executing in
2020-05-24 23:13:21 +05:30
parallel.
2019-12-21 20:55:43 +05:30
2021-01-03 14:25:43 +05:30
If you have a job that unconditionally recreates the cache without
referring to its previous contents, you can skip the download step.
To do so, add `policy: push` to the job.
2020-05-24 23:13:21 +05:30
### `artifacts`
> - Introduced in GitLab Runner v0.7.0 for non-Windows platforms.
> - Windows support was added in GitLab Runner v.1.0.0.
> - From GitLab 9.2, caches are restored before artifacts.
> - Not all executors are [supported](https://docs.gitlab.com/runner/executors/#compatibility-chart).
> - Job artifacts are only collected for successful jobs by default.
2020-10-24 23:57:45 +05:30
`artifacts` is used to specify a list of files and directories that are
2020-05-24 23:13:21 +05:30
attached to the job when it [succeeds, fails, or always](#artifactswhen).
2021-01-03 14:25:43 +05:30
The artifacts are sent to GitLab after the job finishes. They are
available for download in the GitLab UI if the size is not
2020-11-24 15:15:51 +05:30
larger than the [maximum artifact size](../../user/gitlab_com/index.md#gitlab-cicd).
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
[Read more about artifacts](../pipelines/job_artifacts.md).
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
#### `artifacts:paths`
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
Paths are relative to the project directory (`$CI_PROJECT_DIR`) and can't directly
link outside it. Wildcards can be used that follow the [glob](https://en.wikipedia.org/wiki/Glob_(programming))
2020-07-28 23:09:34 +05:30
patterns and:
- In [GitLab Runner 13.0](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2620) and later,
[`doublestar.Glob`](https://pkg.go.dev/github.com/bmatcuk/doublestar@v1.2.2?tab=doc#Match).
- In GitLab Runner 12.10 and earlier,
[`filepath.Match`](https://pkg.go.dev/path/filepath/#Match).
2018-12-13 13:39:08 +05:30
2021-01-03 14:25:43 +05:30
To restrict which jobs a specific job fetches artifacts from, see [dependencies](#dependencies).
2018-12-13 13:39:08 +05:30
2020-05-24 23:13:21 +05:30
Send all files in `binaries` and `.config`:
2018-12-13 13:39:08 +05:30
2020-01-01 13:55:28 +05:30
```yaml
2020-05-24 23:13:21 +05:30
artifacts:
paths:
- binaries/
- .config
2018-12-13 13:39:08 +05:30
```
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
To disable artifact passing, define the job with empty [dependencies](#dependencies):
2019-10-12 21:52:04 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
stage: build
script: make build
dependencies: []
2019-10-12 21:52:04 +05:30
```
2020-05-24 23:13:21 +05:30
You may want to create artifacts only for tagged releases to avoid filling the
build server storage with temporary build artifacts.
2019-10-12 21:52:04 +05:30
2021-01-03 14:25:43 +05:30
Create artifacts only for tags (`default-job` doesn't create artifacts):
2019-10-12 21:52:04 +05:30
2020-05-24 23:13:21 +05:30
```yaml
default-job:
script:
- mvn test -U
except:
- tags
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
release-job:
script:
- mvn package -U
artifacts:
paths:
- target/*.war
only:
- tags
```
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
You can use wildcards for directories too. For example, if you want to get all the files inside the directories that end with `xyz`:
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
```yaml
job:
artifacts:
paths:
- path/*xyz/*
```
2020-03-13 15:44:24 +05:30
2020-06-23 00:09:42 +05:30
#### `artifacts:exclude`
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15122) in GitLab 13.1
> - Requires GitLab Runner 13.1
`exclude` makes it possible to prevent files from being added to an artifacts
archive.
Similar to [`artifacts:paths`](#artifactspaths), `exclude` paths are relative
to the project directory. Wildcards can be used that follow the
[glob](https://en.wikipedia.org/wiki/Glob_(programming)) patterns and
[`filepath.Match`](https://golang.org/pkg/path/filepath/#Match).
For example, to store all files in `binaries/`, but not `*.o` files located in
subdirectories of `binaries/`:
```yaml
artifacts:
paths:
- binaries/
exclude:
- binaries/**/*.o
```
Files matched by [`artifacts:untracked`](#artifactsuntracked) can be excluded using
`artifacts:exclude` too.
2020-05-24 23:13:21 +05:30
#### `artifacts:expose_as`
2019-07-07 11:18:12 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15018) in GitLab 12.5.
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
The `expose_as` keyword can be used to expose [job artifacts](../pipelines/job_artifacts.md)
in the [merge request](../../user/project/merge_requests/index.md) UI.
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
For example, to match a single file:
2019-07-07 11:18:12 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
2020-11-24 15:15:51 +05:30
script: ["echo 'test' > file.txt"]
2020-05-24 23:13:21 +05:30
artifacts:
expose_as: 'artifact 1'
2020-07-28 23:09:34 +05:30
paths: ['file.txt']
2019-07-07 11:18:12 +05:30
```
2021-01-03 14:25:43 +05:30
With this configuration, GitLab adds a link **artifact 1** to the relevant merge request
2020-05-24 23:13:21 +05:30
that points to `file1.txt`.
2019-07-07 11:18:12 +05:30
2021-01-03 14:25:43 +05:30
An example that matches an entire directory:
2019-07-07 11:18:12 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
2020-11-24 15:15:51 +05:30
script: ["mkdir test && echo 'test' > test/file.txt"]
2020-05-24 23:13:21 +05:30
artifacts:
expose_as: 'artifact 1'
2020-07-28 23:09:34 +05:30
paths: ['test/']
2019-07-07 11:18:12 +05:30
```
2020-05-24 23:13:21 +05:30
Note the following:
2019-12-26 22:10:19 +05:30
2020-07-28 23:09:34 +05:30
- Artifacts do not display in the merge request UI when using variables to define the `artifacts:paths`.
2020-05-24 23:13:21 +05:30
- A maximum of 10 job artifacts per merge request can be exposed.
- Glob patterns are unsupported.
2021-01-03 14:25:43 +05:30
- If a directory is specified, the link is to the job [artifacts browser](../pipelines/job_artifacts.md#browsing-artifacts) if there is more than
2020-05-24 23:13:21 +05:30
one file in the directory.
- For exposed single file artifacts with `.html`, `.htm`, `.txt`, `.json`, `.xml`,
and `.log` extensions, if [GitLab Pages](../../administration/pages/index.md) is:
2021-01-03 14:25:43 +05:30
- Enabled, GitLab automatically renders the artifact.
- Not enabled, the file is displayed in the artifacts browser.
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
#### `artifacts:name`
2019-12-26 22:10:19 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 8.6 and GitLab Runner v1.1.0.
2019-12-26 22:10:19 +05:30
2020-10-24 23:57:45 +05:30
Use the `name` directive to define the name of the created artifacts
archive. You can specify a unique name for every archive, which can be
useful when you want to download the archive from GitLab. The `artifacts:name`
2020-05-24 23:13:21 +05:30
variable can make use of any of the [predefined variables](../variables/README.md).
2020-10-24 23:57:45 +05:30
The default name is `artifacts`, which becomes `artifacts.zip` when you download it.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
To create an archive with a name of the current job:
2020-03-13 15:44:24 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
artifacts:
name: "$CI_JOB_NAME"
paths:
- binaries/
2020-03-13 15:44:24 +05:30
```
2020-05-24 23:13:21 +05:30
To create an archive with a name of the current branch or tag including only
the binaries directory:
2020-03-13 15:44:24 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
artifacts:
name: "$CI_COMMIT_REF_NAME"
paths:
- binaries/
2020-03-13 15:44:24 +05:30
```
2021-01-03 14:25:43 +05:30
If your branch-name contains forward slashes
(for example `feature/my-feature`) it's advised to use `$CI_COMMIT_REF_SLUG`
instead of `$CI_COMMIT_REF_NAME` for proper naming of the artifact.
2020-05-24 23:13:21 +05:30
To create an archive with a name of the current job and the current branch or
tag including only the binaries directory:
2020-04-08 14:13:33 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
2020-04-08 14:13:33 +05:30
artifacts:
2020-05-24 23:13:21 +05:30
name: "$CI_JOB_NAME-$CI_COMMIT_REF_NAME"
2020-04-08 14:13:33 +05:30
paths:
2020-05-24 23:13:21 +05:30
- binaries/
2020-04-08 14:13:33 +05:30
```
2020-05-24 23:13:21 +05:30
To create an archive with a name of the current [stage](#stages) and branch name:
2020-03-13 15:44:24 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
artifacts:
name: "$CI_JOB_STAGE-$CI_COMMIT_REF_NAME"
paths:
- binaries/
2020-03-13 15:44:24 +05:30
```
2020-05-24 23:13:21 +05:30
---
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
If you use **Windows Batch** to run your shell scripts you need to replace
`$` with `%`:
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
```yaml
job:
artifacts:
name: "%CI_JOB_STAGE%-%CI_COMMIT_REF_NAME%"
paths:
- binaries/
```
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
If you use **Windows PowerShell** to run your shell scripts you need to replace
`$` with `$env:`:
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
```yaml
job:
artifacts:
name: "$env:CI_JOB_STAGE-$env:CI_COMMIT_REF_NAME"
paths:
- binaries/
```
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
#### `artifacts:untracked`
2019-12-04 20:38:33 +05:30
2020-05-24 23:13:21 +05:30
`artifacts:untracked` is used to add all Git untracked files as artifacts (along
2021-01-03 14:25:43 +05:30
to the paths defined in `artifacts:paths`). `artifacts:untracked` ignores configuration
in the repository's `.gitignore` file.
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
Send all Git untracked files:
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
```yaml
artifacts:
untracked: true
2019-12-04 20:38:33 +05:30
```
2020-05-24 23:13:21 +05:30
Send all Git untracked files and files in `binaries`:
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
```yaml
artifacts:
untracked: true
paths:
- binaries/
```
2019-12-04 20:38:33 +05:30
2020-06-23 00:09:42 +05:30
Send all untracked files but [exclude](#artifactsexclude) `*.txt`:
```yaml
artifacts:
untracked: true
exclude:
2020-11-24 15:15:51 +05:30
- "*.txt"
2020-06-23 00:09:42 +05:30
```
2020-05-24 23:13:21 +05:30
#### `artifacts:when`
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 8.9 and GitLab Runner v1.3.0.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
`artifacts:when` is used to upload artifacts on job failure or despite the
failure.
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
`artifacts:when` can be set to one of the following values:
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
1. `on_success` - upload artifacts only when the job succeeds. This is the default.
1. `on_failure` - upload artifacts only when the job fails.
1. `always` - upload artifacts regardless of the job status.
2020-03-13 15:44:24 +05:30
2021-01-03 14:25:43 +05:30
For example, to upload artifacts only when a job fails:
2020-03-13 15:44:24 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job:
artifacts:
when: on_failure
2020-03-13 15:44:24 +05:30
```
2020-05-24 23:13:21 +05:30
#### `artifacts:expire_in`
2020-03-13 15:44:24 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 8.9 and GitLab Runner v1.3.0.
2020-03-13 15:44:24 +05:30
2020-11-24 15:15:51 +05:30
Use `expire_in` to specify how long artifacts are active before they
expire and are deleted.
The expiration time period begins when the artifact is uploaded and
2020-05-24 23:13:21 +05:30
stored on GitLab. If the expiry time is not defined, it defaults to the
2020-11-24 15:15:51 +05:30
[instance wide setting](../../user/admin_area/settings/continuous_integration.md#default-artifacts-expiration)
2020-07-28 23:09:34 +05:30
(30 days by default).
2020-04-22 19:07:51 +05:30
2020-10-24 23:57:45 +05:30
To override the expiration date and protect artifacts from being automatically deleted:
- Use the **Keep** button on the job page.
- Set the value of `expire_in` to `never`. [Available](https://gitlab.com/gitlab-org/gitlab/-/issues/22761)
in GitLab 13.3 and later.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
After their expiry, artifacts are deleted hourly by default (via a cron job),
and are not accessible anymore.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
The value of `expire_in` is an elapsed time in seconds, unless a unit is
provided. Examples of valid values:
2018-12-05 23:21:45 +05:30
2020-11-24 15:15:51 +05:30
- `'42'`
- `42 seconds`
2020-05-24 23:13:21 +05:30
- `3 mins 4 sec`
- `2 hrs 20 min`
- `2h20min`
- `6 mos 1 day`
- `47 yrs 6 mos and 4d`
- `3 weeks and 2 days`
2020-10-24 23:57:45 +05:30
- `never`
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
To expire artifacts 1 week after being uploaded:
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
```yaml
job:
artifacts:
expire_in: 1 week
```
2018-12-05 23:21:45 +05:30
2020-11-24 15:15:51 +05:30
The latest artifacts for refs are locked against deletion, and kept regardless of
the expiry time. [Introduced in](https://gitlab.com/gitlab-org/gitlab/-/issues/16267)
GitLab 13.0 behind a disabled feature flag, and [made the default behavior](https://gitlab.com/gitlab-org/gitlab/-/issues/229936)
in GitLab 13.4.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
#### `artifacts:reports`
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
The [`artifacts:reports` keyword](../pipelines/job_artifacts.md#artifactsreports)
is used for collecting test reports, code quality reports, and security reports from jobs.
It also exposes these reports in GitLab's UI (merge requests, pipeline views, and security dashboards).
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
These are the available report types:
| Parameter | Description |
|--------------------------------------------------------------------------------------------------------------------------------------|-------------|
| [`artifacts:reports:cobertura`](../pipelines/job_artifacts.md#artifactsreportscobertura) | The `cobertura` report collects Cobertura coverage XML files. |
2020-07-28 23:09:34 +05:30
| [`artifacts:reports:codequality`](../pipelines/job_artifacts.md#artifactsreportscodequality) | The `codequality` report collects CodeQuality issues. |
2020-11-24 15:15:51 +05:30
| [`artifacts:reports:container_scanning`](../pipelines/job_artifacts.md#artifactsreportscontainer_scanning) **(ULTIMATE)** | The `container_scanning` report collects Container Scanning vulnerabilities. |
| [`artifacts:reports:dast`](../pipelines/job_artifacts.md#artifactsreportsdast) **(ULTIMATE)** | The `dast` report collects Dynamic Application Security Testing vulnerabilities. |
| [`artifacts:reports:dependency_scanning`](../pipelines/job_artifacts.md#artifactsreportsdependency_scanning) **(ULTIMATE)** | The `dependency_scanning` report collects Dependency Scanning vulnerabilities. |
2020-10-24 23:57:45 +05:30
| [`artifacts:reports:dotenv`](../pipelines/job_artifacts.md#artifactsreportsdotenv) | The `dotenv` report collects a set of environment variables. |
| [`artifacts:reports:junit`](../pipelines/job_artifacts.md#artifactsreportsjunit) | The `junit` report collects JUnit XML files. |
2020-11-24 15:15:51 +05:30
| [`artifacts:reports:license_management`](../pipelines/job_artifacts.md#artifactsreportslicense_management) **(ULTIMATE)** | The `license_management` report collects Licenses (*removed from GitLab 13.0*). |
| [`artifacts:reports:license_scanning`](../pipelines/job_artifacts.md#artifactsreportslicense_scanning) **(ULTIMATE)** | The `license_scanning` report collects Licenses. |
| [`artifacts:reports:load_performance`](../pipelines/job_artifacts.md#artifactsreportsload_performance) **(PREMIUM)** | The `load_performance` report collects load performance metrics. |
| [`artifacts:reports:metrics`](../pipelines/job_artifacts.md#artifactsreportsmetrics) **(PREMIUM)** | The `metrics` report collects Metrics. |
| [`artifacts:reports:performance`](../pipelines/job_artifacts.md#artifactsreportsperformance) **(PREMIUM)** | The `performance` report collects Browser Performance metrics. |
| [`artifacts:reports:sast`](../pipelines/job_artifacts.md#artifactsreportssast) **(ULTIMATE)** | The `sast` report collects Static Application Security Testing vulnerabilities. |
2020-10-24 23:57:45 +05:30
| [`artifacts:reports:terraform`](../pipelines/job_artifacts.md#artifactsreportsterraform) | The `terraform` report collects Terraform `tfplan.json` files. |
2020-05-24 23:13:21 +05:30
#### `dependencies`
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 8.6 and GitLab Runner v1.1.1.
2018-12-05 23:21:45 +05:30
2021-01-03 14:25:43 +05:30
By default, all [`artifacts`](#artifacts) from previous [stages](#stages)
are passed to each job. However, you can use the `dependencies` parameter to
define a limited list of jobs to fetch artifacts from. You can also set a job to download no artifacts at all.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
To use this feature, define `dependencies` in context of the job and pass
2020-10-24 23:57:45 +05:30
a list of all previous jobs the artifacts should be downloaded from.
2019-07-07 11:18:12 +05:30
2021-01-03 14:25:43 +05:30
You can define jobs from stages that were executed before the current one.
An error occurs if you define jobs from the current or an upcoming stage.
To prevent a job from downloading artifacts, define an empty array.
When you use `dependencies`, the status of the previous job is not considered.
If a job fails or it's a manual job that was not run, no error occurs.
The following example defines two jobs with artifacts: `build:osx` and
2020-05-24 23:13:21 +05:30
`build:linux`. When the `test:osx` is executed, the artifacts from `build:osx`
2021-01-03 14:25:43 +05:30
are downloaded and extracted in the context of the build. The same happens
2020-05-24 23:13:21 +05:30
for `test:linux` and artifacts from `build:linux`.
2019-03-02 22:35:43 +05:30
2021-01-03 14:25:43 +05:30
The job `deploy` downloads artifacts from all previous jobs because of
2020-05-24 23:13:21 +05:30
the [stage](#stages) precedence:
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
build:osx:
stage: build
script: make build:osx
artifacts:
paths:
- binaries/
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
build:linux:
stage: build
script: make build:linux
artifacts:
paths:
- binaries/
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
test:osx:
stage: test
script: make test:osx
dependencies:
- build:osx
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
test:linux:
stage: test
script: make test:linux
dependencies:
- build:linux
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
deploy:
stage: deploy
script: make deploy
2018-12-05 23:21:45 +05:30
```
2021-01-03 14:25:43 +05:30
##### When a dependent job fails
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 10.3.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
If the artifacts of the job that is set as a dependency have been
[expired](#artifactsexpire_in) or
[erased](../pipelines/job_artifacts.md#erasing-artifacts), then
2021-01-03 14:25:43 +05:30
the dependent job fails.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
You can ask your administrator to
[flip this switch](../../administration/job_artifacts.md#validation-for-dependencies)
and bring back the old behavior.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
### `coverage`
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/20428) in GitLab 8.17.
2019-03-02 22:35:43 +05:30
2020-11-24 15:15:51 +05:30
Use `coverage` to configure how code coverage is extracted from the
2020-05-24 23:13:21 +05:30
job output.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
Regular expressions are the only valid kind of value expected here. So, using
2021-01-03 14:25:43 +05:30
surrounding `/` is mandatory to consistently and explicitly represent
2020-05-24 23:13:21 +05:30
a regular expression string. You must escape special characters if you want to
match them literally.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
A simple example:
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
job1:
script: rspec
coverage: '/Code coverage: \d+\.\d+/'
2019-02-15 15:39:39 +05:30
```
2020-05-24 23:13:21 +05:30
### `retry`
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/3442) in GitLab 9.5.
2020-10-24 23:57:45 +05:30
> - [Behavior expanded](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3515) in GitLab 11.5 to control which failures to retry on.
2020-05-24 23:13:21 +05:30
2021-01-03 14:25:43 +05:30
Use `retry` to configure how many times a job is retried in
2020-05-24 23:13:21 +05:30
case of a failure.
2021-01-03 14:25:43 +05:30
When a job fails, the job is processed again,
until the limit specified by the `retry` keyword is reached.
2020-05-24 23:13:21 +05:30
2021-01-03 14:25:43 +05:30
If `retry` is set to `2`, and a job succeeds in a second run (first retry), it is not retried.
The `retry` value must be a positive integer, from `0` to `2`
(two retries maximum, three runs in total).
2020-05-24 23:13:21 +05:30
2021-01-03 14:25:43 +05:30
This example retries all failure cases:
2019-12-04 20:38:33 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
script: rspec
retry: 2
2019-12-04 20:38:33 +05:30
```
2021-01-03 14:25:43 +05:30
By default, a job is retried on all failure cases. To have better control
2020-10-24 23:57:45 +05:30
over which failures to retry, `retry` can be a hash with the following keys:
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
- `max`: The maximum number of retries.
- `when`: The failure cases to retry.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
To retry only runner system failures at maximum two times:
2018-12-05 23:21:45 +05:30
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
script: rspec
retry:
max: 2
when: runner_system_failure
2019-03-02 22:35:43 +05:30
```
2018-12-05 23:21:45 +05:30
2021-01-03 14:25:43 +05:30
If there is another failure, other than a runner system failure, the job
is not retried.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
To retry on multiple failure cases, `when` can also be an array of failures:
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
```yaml
test:
script: rspec
retry:
max: 2
when:
- runner_system_failure
- stuck_or_timeout_failure
```
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
Possible values for `when` are:
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
<!--
2021-01-03 14:25:43 +05:30
If you change any of the values below, make sure to update the `RETRY_WHEN_IN_DOCUMENTATION`
array in `spec/lib/gitlab/ci/config/entry/retry_spec.rb`.
The test there makes sure that all documented
values are valid as a configuration option and therefore should always
2020-05-24 23:13:21 +05:30
stay in sync with this documentation.
-->
2019-12-21 20:55:43 +05:30
2020-05-24 23:13:21 +05:30
- `always`: Retry on any failure (default).
- `unknown_failure`: Retry when the failure reason is unknown.
- `script_failure`: Retry when the script failed.
- `api_failure`: Retry on API failure.
- `stuck_or_timeout_failure`: Retry when the job got stuck or timed out.
- `runner_system_failure`: Retry if there was a runner system failure (for example, job setup failed).
- `missing_dependency_failure`: Retry if a dependency was missing.
- `runner_unsupported`: Retry if the runner was unsupported.
- `stale_schedule`: Retry if a delayed job could not be executed.
- `job_execution_timeout`: Retry if the script exceeded the maximum execution time set for the job.
- `archived_failure`: Retry if the job is archived and can't be run.
- `unmet_prerequisites`: Retry if the job failed to complete prerequisite tasks.
- `scheduler_failure`: Retry if the scheduler failed to assign the job to a runner.
- `data_integrity_failure`: Retry if there was a structural integrity problem detected.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
You can specify the number of [retry attempts for certain stages of job execution](#job-stages-attempts) using variables.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
### `timeout`
2018-12-05 23:21:45 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14887) in GitLab 12.3.
2018-12-05 23:21:45 +05:30
2020-11-24 15:15:51 +05:30
Use `timeout` to configure a timeout for a specific job. For example:
2019-02-15 15:39:39 +05:30
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
build:
script: build.sh
timeout: 3 hours 30 minutes
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
test:
script: rspec
timeout: 3h 30m
2019-03-02 22:35:43 +05:30
```
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
The job-level timeout can exceed the
[project-level timeout](../pipelines/settings.md#timeout) but can't
2020-10-24 23:57:45 +05:30
exceed the runner-specific timeout.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
### `parallel`
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/21480) in GitLab 11.5.
2018-12-05 23:21:45 +05:30
2020-11-24 15:15:51 +05:30
Use `parallel` to configure how many instances of a job to run in
2020-05-24 23:13:21 +05:30
parallel. This value has to be greater than or equal to two (2) and less than or equal to 50.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
This creates N instances of the same job that run in parallel. They are named
sequentially from `job_name 1/N` to `job_name N/N`.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
For every job, `CI_NODE_INDEX` and `CI_NODE_TOTAL` [environment variables](../variables/README.md#predefined-environment-variables) are set.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
Marking a job to be run in parallel requires adding `parallel` to your configuration
file. For example:
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
script: rspec
parallel: 5
2019-03-02 22:35:43 +05:30
```
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
Parallelize tests suites across parallel jobs.
Different languages have different tools to facilitate this.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
A simple example using [Semaphore Test Boosters](https://github.com/renderedtext/test-boosters) and RSpec to run some Ruby tests:
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
```ruby
# Gemfile
source 'https://rubygems.org'
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
gem 'rspec'
gem 'semaphore_test_boosters'
2019-03-02 22:35:43 +05:30
```
2019-02-15 15:39:39 +05:30
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
test:
parallel: 3
2019-03-02 22:35:43 +05:30
script:
2020-05-24 23:13:21 +05:30
- bundle
- bundle exec rspec_booster --job $CI_NODE_INDEX/$CI_NODE_TOTAL
2019-03-02 22:35:43 +05:30
```
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
CAUTION: **Caution:**
Please be aware that semaphore_test_boosters reports usages statistics to the author.
2019-02-15 15:39:39 +05:30
2020-05-24 23:13:21 +05:30
You can then navigate to the **Jobs** tab of a new pipeline build and see your RSpec
job split into three separate jobs.
2018-12-05 23:21:45 +05:30
2020-10-24 23:57:45 +05:30
#### Parallel `matrix` jobs
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15356) in GitLab 13.3.
2020-11-24 15:15:51 +05:30
Use `matrix:` to configure different variables for jobs that are running in parallel.
2020-10-24 23:57:45 +05:30
There can be from 2 to 50 jobs.
2021-01-03 14:25:43 +05:30
[In GitLab 13.5](https://gitlab.com/gitlab-org/gitlab/-/issues/26362) and later,
you can have one-dimensional matrices with a single job.
The ability to have one-dimensional matrices is [deployed behind a feature flag](../../user/feature_flags.md),
enabled by default. It's enabled on GitLab.com. For self-managed GitLab instances,
administrators can opt to disable it by [disabling the `one_dimensional_matrix:` feature flag](../../administration/feature_flags.md). **(CORE ONLY)**
2020-10-24 23:57:45 +05:30
Every job gets the same `CI_NODE_TOTAL` [environment variable](../variables/README.md#predefined-environment-variables) value, and a unique `CI_NODE_INDEX` value.
```yaml
deploystacks:
stage: deploy
script:
- bin/deploy
parallel:
matrix:
- PROVIDER: aws
STACK:
- monitoring
- app1
- app2
- PROVIDER: ovh
STACK: [monitoring, backup, app]
- PROVIDER: [gcp, vultr]
STACK: [data, processing]
```
This generates 10 parallel `deploystacks` jobs, each with different values for `PROVIDER` and `STACK`:
```plaintext
2020-11-24 15:15:51 +05:30
deploystacks: [aws, monitoring]
deploystacks: [aws, app1]
deploystacks: [aws, app2]
deploystacks: [ovh, monitoring]
deploystacks: [ovh, backup]
deploystacks: [ovh, app]
deploystacks: [gcp, data]
deploystacks: [gcp, processing]
deploystacks: [vultr, data]
deploystacks: [vultr, processing]
2020-10-24 23:57:45 +05:30
```
2020-11-24 15:15:51 +05:30
Job naming style [was improved](https://gitlab.com/gitlab-org/gitlab/-/issues/230452) in GitLab 13.4.
2020-05-24 23:13:21 +05:30
### `trigger`
2018-12-05 23:21:45 +05:30
2020-06-23 00:09:42 +05:30
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/8997) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.8.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/199224) to GitLab Core in 12.8.
2018-12-05 23:21:45 +05:30
2020-11-24 15:15:51 +05:30
Use `trigger` to define a downstream pipeline trigger. When GitLab starts a job created
with a `trigger` definition, a downstream pipeline is created.
2018-12-05 23:21:45 +05:30
2021-01-03 14:25:43 +05:30
Jobs with `trigger` can only use a [limited set of keywords](../multi_project_pipelines.md#limitations).
For example, you can't run commands with [`script`](#script), [`before_script`](#before_script-and-after_script),
or [`after_script`](#before_script-and-after_script).
2020-11-24 15:15:51 +05:30
You can use this keyword to create two different types of downstream pipelines:
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
- [Multi-project pipelines](../multi_project_pipelines.md#creating-multi-project-pipelines-from-gitlab-ciyml)
- [Child pipelines](../parent_child_pipelines.md)
2018-12-05 23:21:45 +05:30
2021-01-03 14:25:43 +05:30
[In GitLab 13.2](https://gitlab.com/gitlab-org/gitlab/-/issues/197140/) and later, you can
view which job triggered a downstream pipeline. In the [pipeline graph](../pipelines/index.md#visualize-pipelines),
hover over the downstream pipeline job.
2020-07-28 23:09:34 +05:30
2021-01-03 14:25:43 +05:30
In [GitLab 13.5](https://gitlab.com/gitlab-org/gitlab/-/issues/201938) and later, you
can use [`when:manual`](#whenmanual) in the same job as `trigger`. In GitLab 13.4 and
earlier, using them together causes the error `jobs:#{job-name} when should be on_success, on_failure or always`.
It is deployed behind the `:ci_manual_bridges` [feature flag](../../user/feature_flags.md), which is **enabled by default**.
[GitLab administrators with access to the Rails console](../../administration/feature_flags.md)
can opt to disable it.
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
#### Simple `trigger` syntax for multi-project pipelines
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
The simplest way to configure a downstream trigger is to use `trigger` keyword
with a full path to a downstream project:
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
```yaml
rspec:
stage: test
script: bundle exec rspec
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
staging:
stage: deploy
trigger: my/deployment
```
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
#### Complex `trigger` syntax for multi-project pipelines
2018-12-05 23:21:45 +05:30
2021-01-03 14:25:43 +05:30
You can configure a branch name that GitLab uses to create
2020-05-24 23:13:21 +05:30
a downstream pipeline with:
2018-12-05 23:21:45 +05:30
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
rspec:
stage: test
script: bundle exec rspec
staging:
stage: deploy
trigger:
project: my/deployment
branch: stable
2018-12-05 23:21:45 +05:30
```
2021-01-03 14:25:43 +05:30
To mirror the status from a triggered pipeline:
2018-12-05 23:21:45 +05:30
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
trigger_job:
trigger:
project: my/project
strategy: depend
```
2018-12-05 23:21:45 +05:30
2021-01-03 14:25:43 +05:30
To mirror the status from an upstream pipeline:
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
```yaml
upstream_bridge:
stage: test
needs:
pipeline: other/project
2018-12-05 23:21:45 +05:30
```
2020-05-24 23:13:21 +05:30
#### `trigger` syntax for child pipeline
2019-07-07 11:18:12 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/16094) in GitLab 12.7.
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
To create a [child pipeline](../parent_child_pipelines.md), specify the path to the
YAML file containing the CI config of the child pipeline:
2019-07-07 11:18:12 +05:30
```yaml
2020-05-24 23:13:21 +05:30
trigger_job:
trigger:
include: path/to/child-pipeline.yml
2019-07-07 11:18:12 +05:30
```
2020-05-24 23:13:21 +05:30
Similar to [multi-project pipelines](../multi_project_pipelines.md#mirroring-status-from-triggered-pipeline),
it's possible to mirror the status from a triggered pipeline:
2019-07-07 11:18:12 +05:30
```yaml
2020-05-24 23:13:21 +05:30
trigger_job:
trigger:
include:
- local: path/to/child-pipeline.yml
strategy: depend
2019-07-07 11:18:12 +05:30
```
2020-05-24 23:13:21 +05:30
##### Trigger child pipeline with generated configuration file
2019-07-07 11:18:12 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/35632) in GitLab 12.9.
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
You can also trigger a child pipeline from a [dynamically generated configuration file](../parent_child_pipelines.md#dynamic-child-pipelines):
2019-07-07 11:18:12 +05:30
```yaml
2020-05-24 23:13:21 +05:30
generate-config:
stage: build
script: generate-ci-config > generated-config.yml
artifacts:
paths:
- generated-config.yml
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
child-pipeline:
stage: test
trigger:
include:
- artifact: generated-config.yml
job: generate-config
2019-07-07 11:18:12 +05:30
```
2020-05-24 23:13:21 +05:30
The `generated-config.yml` is extracted from the artifacts and used as the configuration
for triggering the child pipeline.
2019-03-02 22:35:43 +05:30
2021-01-03 14:25:43 +05:30
##### Trigger child pipeline with files from another project
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/205157) in GitLab 13.5.
To trigger child pipelines with files from another private project under the same
GitLab instance, use [`include:file`](#includefile):
```yaml
child-pipeline:
trigger:
include:
- project: 'my-group/my-pipeline-library'
ref: 'master'
file: '/path/to/child-pipeline.yml'
```
2020-05-24 23:13:21 +05:30
#### Linking pipelines with `trigger:strategy`
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
By default, the `trigger` job completes with the `success` status
as soon as the downstream pipeline is created.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
To force the `trigger` job to wait for the downstream (multi-project or child) pipeline to complete, use
2021-01-03 14:25:43 +05:30
`strategy: depend`. This setting makes the trigger job wait with a "running" status until the triggered
pipeline completes. At that point, the `trigger` job completes and displays the same status as
2020-05-24 23:13:21 +05:30
the downstream job.
2019-03-02 22:35:43 +05:30
```yaml
2020-05-24 23:13:21 +05:30
trigger_job:
trigger:
include: path/to/child-pipeline.yml
strategy: depend
2019-03-02 22:35:43 +05:30
```
2021-01-03 14:25:43 +05:30
This setting can help keep your pipeline execution linear. In the example above, jobs from
subsequent stages wait for the triggered pipeline to successfully complete before
starting, which reduces parallelization.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
#### Trigger a pipeline by API call
2019-03-02 22:35:43 +05:30
2021-01-03 14:25:43 +05:30
To force a rebuild of a specific branch, tag, or commit, you can use an API call
with a trigger token.
2019-03-02 22:35:43 +05:30
2021-01-03 14:25:43 +05:30
The trigger token is different than the [`trigger`](#trigger) parameter.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
[Read more in the triggers documentation.](../triggers/README.md)
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
### `interruptible`
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/32022) in GitLab 12.3.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
`interruptible` is used to indicate that a job should be canceled if made redundant by a newer pipeline run. Defaults to `false`.
2021-01-03 14:25:43 +05:30
This value is used only if the [automatic cancellation of redundant pipelines feature](../pipelines/settings.md#auto-cancel-pending-pipelines)
2020-05-24 23:13:21 +05:30
is enabled.
2019-03-02 22:35:43 +05:30
2021-01-03 14:25:43 +05:30
When enabled, a pipeline on the same branch is canceled when:
2019-03-02 22:35:43 +05:30
2020-07-28 23:09:34 +05:30
- It's made redundant by a newer pipeline run.
2020-05-24 23:13:21 +05:30
- Either all jobs are set as interruptible, or any uninterruptible jobs haven't started.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
Set jobs as interruptible that can be safely canceled once started (for instance, a build job).
2019-03-02 22:35:43 +05:30
2021-01-03 14:25:43 +05:30
Pending jobs are always considered interruptible.
2020-05-24 23:13:21 +05:30
Here is a simple example:
2019-09-04 21:01:54 +05:30
```yaml
2020-05-24 23:13:21 +05:30
stages:
- stage1
- stage2
- stage3
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
step-1:
stage: stage1
2019-09-04 21:01:54 +05:30
script:
2020-05-24 23:13:21 +05:30
- echo "Can be canceled."
interruptible: true
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
step-2:
stage: stage2
script:
- echo "Can not be canceled."
2019-09-04 21:01:54 +05:30
2020-05-24 23:13:21 +05:30
step-3:
stage: stage3
2019-09-04 21:01:54 +05:30
script:
2021-01-03 14:25:43 +05:30
- echo "Because step-2 can not be canceled, this step can never be canceled, even though it's set as interruptible."
2020-05-24 23:13:21 +05:30
interruptible: true
2019-09-04 21:01:54 +05:30
```
2021-01-03 14:25:43 +05:30
In the example above, a new pipeline run causes an existing running pipeline to be:
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
- Canceled, if only `step-1` is running or pending.
- Not canceled, once `step-2` starts running.
2019-03-02 22:35:43 +05:30
2021-01-03 14:25:43 +05:30
When an uninterruptible job is running, the pipeline can never be canceled, regardless of the final job's state.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
### `resource_group`
2019-03-02 22:35:43 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15536) in GitLab 12.7.
2019-03-02 22:35:43 +05:30
2020-10-24 23:57:45 +05:30
Sometimes running multiple jobs or pipelines at the same time in an environment
2020-05-24 23:13:21 +05:30
can lead to errors during the deployment.
2019-03-02 22:35:43 +05:30
2020-05-24 23:13:21 +05:30
To avoid these errors, the `resource_group` attribute can be used to ensure that
2021-01-03 14:25:43 +05:30
the runner doesn't run certain jobs simultaneously. Resource groups behave similar
to semaphores in other programming languages.
2020-05-24 23:13:21 +05:30
When the `resource_group` key is defined for a job in `.gitlab-ci.yml`,
job executions are mutually exclusive across different pipelines for the same project.
If multiple jobs belonging to the same resource group are enqueued simultaneously,
2021-01-03 14:25:43 +05:30
only one of the jobs is picked by the runner. The other jobs wait until the
2020-05-24 23:13:21 +05:30
`resource_group` is free.
Here is a simple example:
```yaml
deploy-to-production:
script: deploy
resource_group: production
2019-03-02 22:35:43 +05:30
```
2021-01-03 14:25:43 +05:30
In this case, two `deploy-to-production` jobs in two separate pipelines can never run at the same time. As a result,
you can ensure that concurrent deployments never happen to the production environment.
2020-05-24 23:13:21 +05:30
There can be multiple `resource_group`s defined per environment. A good use case for this
2021-01-03 14:25:43 +05:30
is when deploying to physical devices. You may have multiple physical devices that
can be deployed to, but there can be only one deployment per device at any given time.
2020-05-24 23:13:21 +05:30
2021-01-03 14:25:43 +05:30
The `resource_group` value can only contain letters, digits, `-`, `_`, `/`, `$`, `{`, `}`, `.`, and spaces.
2020-05-24 23:13:21 +05:30
It can't start or end with `/`.
2019-03-02 22:35:43 +05:30
2020-06-23 00:09:42 +05:30
For more information, see [Deployments Safety](../environments/deployment_safety.md).
2020-07-28 23:09:34 +05:30
### `release`
> [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/19298) in GitLab 13.2.
2020-10-24 23:57:45 +05:30
`release` indicates that the job creates a [Release](../../user/project/releases/index.md).
2020-07-28 23:09:34 +05:30
These methods are supported:
- [`tag_name`](#releasetag_name)
- [`name`](#releasename) (optional)
- [`description`](#releasedescription) (optional)
- [`ref`](#releaseref) (optional)
- [`milestones`](#releasemilestones) (optional)
- [`released_at`](#releasereleased_at) (optional)
The Release is created only if the job processes without error. If the Rails API
returns an error during Release creation, the `release` job fails.
#### `release-cli` Docker image
The Docker image to use for the `release-cli` must be specified, using the following directive:
```yaml
image: registry.gitlab.com/gitlab-org/release-cli:latest
```
#### Script
All jobs require a `script` tag at a minimum. A `:release` job can use the output of a
`:script` tag, but if this is not necessary, a placeholder script can be used, for example:
```yaml
script:
- echo 'release job'
```
An [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/223856) exists to remove this requirement in an upcoming version of GitLab.
A pipeline can have multiple `release` jobs, for example:
```yaml
ios-release:
script:
- echo 'iOS release job'
release:
2020-11-24 15:15:51 +05:30
tag_name: v1.0.0-ios
description: 'iOS release v1.0.0'
2020-07-28 23:09:34 +05:30
android-release:
script:
- echo 'Android release job'
release:
2020-11-24 15:15:51 +05:30
tag_name: v1.0.0-android
description: 'Android release v1.0.0'
2020-07-28 23:09:34 +05:30
```
#### `release:tag_name`
The `tag_name` must be specified. It can refer to an existing Git tag or can be specified by the user.
When the specified tag doesn't exist in the repository, a new tag is created from the associated SHA of the pipeline.
For example, when creating a Release from a Git tag:
```yaml
job:
release:
tag_name: $CI_COMMIT_TAG
description: changelog.txt
```
It is also possible to create any unique tag, in which case `only: tags` is not mandatory.
A semantic versioning example:
```yaml
job:
release:
tag_name: ${MAJOR}_${MINOR}_${REVISION}
description: changelog.txt
```
- The Release is created only if the job's main script succeeds.
- If the Release already exists, it is not updated and the job with the `release` keyword fails.
- The `release` section executes after the `script` tag and before the `after_script`.
#### `release:name`
The Release name. If omitted, it is populated with the value of `release: tag_name`.
#### `release:description`
Specifies the longer description of the Release.
#### `release:ref`
If the `release: tag_name` doesnt exist yet, the release is created from `ref`.
`ref` can be a commit SHA, another tag name, or a branch name.
#### `release:milestones`
The title of each milestone the release is associated with.
#### `release:released_at`
The date and time when the release is ready. Defaults to the current date and time if not
2021-01-03 14:25:43 +05:30
defined. Should be enclosed in quotes and expressed in ISO 8601 format.
```json
released_at: '2021-03-15T08:00:00Z'
```
2020-07-28 23:09:34 +05:30
#### Complete example for `release`
Combining the individual examples given above for `release` results in the following
code snippets. There are two options, depending on how you generate the
tags. These options cannot be used together, so choose one:
- To create a release when you push a Git tag, or when you add a Git tag
in the UI by going to **Repository > Tags**:
```yaml
release_job:
stage: release
image: registry.gitlab.com/gitlab-org/release-cli:latest
rules:
- if: $CI_COMMIT_TAG # Run this job when a tag is created manually
script:
- echo 'running release_job'
release:
2020-11-24 15:15:51 +05:30
name: 'Release $CI_COMMIT_TAG'
description: 'Created using the release-cli $EXTRA_DESCRIPTION' # $EXTRA_DESCRIPTION must be defined
tag_name: '$CI_COMMIT_TAG' # elsewhere in the pipeline.
ref: '$CI_COMMIT_TAG'
milestones:
- 'm1'
- 'm2'
- 'm3'
2021-01-03 14:25:43 +05:30
released_at: '2020-07-15T08:00:00Z' # Optional, is auto generated if not defined, or can use a variable.
2020-07-28 23:09:34 +05:30
```
2020-10-24 23:57:45 +05:30
- To create a release automatically when commits are pushed or merged to the default branch,
2020-07-28 23:09:34 +05:30
using a new Git tag that is defined with variables:
2020-11-24 15:15:51 +05:30
NOTE: **Note:**
Environment variables set in `before_script` or `script` are not available for expanding
in the same job. Read more about
[potentially making variables available for expanding](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6400).
2020-10-24 23:57:45 +05:30
2020-07-28 23:09:34 +05:30
```yaml
2020-10-24 23:57:45 +05:30
prepare_job:
stage: prepare # This stage must run before the release stage
rules:
- if: $CI_COMMIT_TAG
when: never # Do not run this job when a tag is created manually
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH # Run this job when commits are pushed or merged to the default branch
script:
- echo "EXTRA_DESCRIPTION=some message" >> variables.env # Generate the EXTRA_DESCRIPTION and TAG environment variables
- echo "TAG=v$(cat VERSION)" >> variables.env # and append to the variables.env file
artifacts:
reports:
dotenv: variables.env # Use artifacts:reports:dotenv to expose the variables to other jobs
2020-07-28 23:09:34 +05:30
release_job:
stage: release
image: registry.gitlab.com/gitlab-org/release-cli:latest
2020-10-24 23:57:45 +05:30
needs:
2020-11-24 15:15:51 +05:30
- job: prepare_job
artifacts: true
2020-07-28 23:09:34 +05:30
rules:
- if: $CI_COMMIT_TAG
2020-11-24 15:15:51 +05:30
when: never # Do not run this job when a tag is created manually
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH # Run this job when commits are pushed or merged to the default branch
2020-07-28 23:09:34 +05:30
script:
2020-10-24 23:57:45 +05:30
- echo 'running release_job for $TAG'
2020-07-28 23:09:34 +05:30
release:
2020-11-24 15:15:51 +05:30
name: 'Release $TAG'
description: 'Created using the release-cli $EXTRA_DESCRIPTION' # $EXTRA_DESCRIPTION and the $TAG
tag_name: '$TAG' # variables must be defined elsewhere
ref: '$CI_COMMIT_SHA' # in the pipeline. For example, in the
milestones: # prepare_job
- 'm1'
- 'm2'
- 'm3'
2021-01-03 14:25:43 +05:30
released_at: '2020-07-15T08:00:00Z' # Optional, is auto generated if not defined, or can use a variable.
2020-07-28 23:09:34 +05:30
```
2021-01-03 14:25:43 +05:30
#### Release assets as Generic packages
You can use [Generic packages](../../user/packages/generic_packages/) to host your release assets.
For a complete example of how to do this, see the [example in the repository](https://gitlab.com/gitlab-org/release-cli/-/tree/master/docs/examples/release-assets-as-generic-package/).
2020-07-28 23:09:34 +05:30
#### `releaser-cli` command line
The entries under the `:release` node are transformed into a `bash` command line and sent
to the Docker container, which contains the [release-cli](https://gitlab.com/gitlab-org/release-cli).
You can also call the `release-cli` directly from a `script` entry.
The YAML described above would be translated into a CLI command like this:
```shell
release-cli create --name "Release $CI_COMMIT_SHA" --description "Created using the release-cli $EXTRA_DESCRIPTION" --tag-name "v${MAJOR}.${MINOR}.${REVISION}" --ref "$CI_COMMIT_SHA" --released-at "2020-07-15T08:00:00Z" --milestone "m1" --milestone "m2" --milestone "m3"
```
2020-11-24 15:15:51 +05:30
### `secrets`
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33014) in GitLab 13.4.
`secrets` indicates the [CI Secrets](../secrets/index.md) this job needs. It should be a hash,
2021-01-03 14:25:43 +05:30
and the keys should be the names of the environment variables that are made available to the job.
The value of each secret is saved in a temporary file. This file's path is stored in these
environment variables.
2020-11-24 15:15:51 +05:30
#### `secrets:vault` **(PREMIUM)**
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/28321) in GitLab 13.4.
`vault` keyword specifies secrets provided by [Hashicorp's Vault](https://www.vaultproject.io/).
2021-01-03 14:25:43 +05:30
This syntax has multiple forms. The shortest form assumes the use of the
2020-11-24 15:15:51 +05:30
[KV-V2](https://www.vaultproject.io/docs/secrets/kv/kv-v2) secrets engine,
mounted at the default path `kv-v2`. The last part of the secret's path is the
field to fetch the value for:
```yaml
job:
secrets:
DATABASE_PASSWORD:
2021-01-03 14:25:43 +05:30
vault: production/db/password # translates to secret `kv-v2/data/production/db`, field `password`
2020-11-24 15:15:51 +05:30
```
You can specify a custom secrets engine path by adding a suffix starting with `@`:
```yaml
job:
secrets:
DATABASE_PASSWORD:
2021-01-03 14:25:43 +05:30
vault: production/db/password@ops # translates to secret `ops/data/production/db`, field `password`
2020-11-24 15:15:51 +05:30
```
In the detailed form of the syntax, you can specify all details explicitly:
```yaml
job:
secrets:
DATABASE_PASSWORD: # translates to secret `ops/data/production/db`, field `password`
vault:
engine:
name: kv-v2
path: ops
path: production/db
field: password
```
2019-07-07 11:18:12 +05:30
### `pages`
2019-03-02 22:35:43 +05:30
`pages` is a special job that is used to upload static content to GitLab that
can be used to serve your website. It has a special syntax, so the two
requirements below must be met:
- Any static content must be placed under a `public/` directory.
- `artifacts` with a path to the `public/` directory must be defined.
The example below simply moves all files from the root of the project to the
2020-05-24 23:13:21 +05:30
`public/` directory. The `.public` workaround is so `cp` does not also copy
2019-03-02 22:35:43 +05:30
`public/` to itself in an infinite loop:
```yaml
pages:
stage: deploy
script:
- mkdir .public
- cp -r * .public
- mv .public public
artifacts:
paths:
- public
only:
- master
```
Read more on [GitLab Pages user documentation](../../user/project/pages/index.md).
2018-12-05 23:21:45 +05:30
2020-05-24 23:13:21 +05:30
## `variables`
2018-05-09 12:01:36 +05:30
> Introduced in GitLab Runner v0.5.0.
2021-01-03 14:25:43 +05:30
Variables are configurable values that are passed to jobs. They can be set
globally and per-job.
There are two types of variables.
- [Custom variables](../variables/README.md#custom-environment-variables):
You can define their values in the `.gitlab-ci.yml` file, in the GitLab UI,
or by using the API.
- [Predefined variables](../variables/predefined_variables.md):
These values are set by the runner itself.
One example is `CI_COMMIT_REF_NAME`, which is the branch or tag the project is built for.
2018-05-09 12:01:36 +05:30
2021-01-03 14:25:43 +05:30
After you define a variable, you can use it in all executed commands and scripts.
2018-05-09 12:01:36 +05:30
2021-01-03 14:25:43 +05:30
Variables are meant for non-sensitive project configuration, for example:
2018-05-09 12:01:36 +05:30
```yaml
variables:
DATABASE_URL: "postgres://postgres@postgres/my_database"
```
2021-01-03 14:25:43 +05:30
You can use integers and strings for the variable's name and value.
You cannot use floats.
If you define a variable at the top level of the `gitlab-ci.yml` file, it is global,
meaning it applies to all jobs.
If you define a variable within a job, it's available to that job only.
2018-05-09 12:01:36 +05:30
2021-01-03 14:25:43 +05:30
If a variable of the same name is defined globally and for a specific job, the
[job-specific variable is used](../variables/README.md#priority-of-environment-variables).
All YAML-defined variables are also set to any linked
[service containers](../docker/using_docker_images.md#what-is-a-service).
2018-05-09 12:01:36 +05:30
2020-03-13 15:44:24 +05:30
[YAML anchors for variables](#yaml-anchors-for-variables) are available.
2018-05-09 12:01:36 +05:30
2020-04-22 19:07:51 +05:30
Learn more about [variables and their priority](../variables/README.md).
2020-01-01 13:55:28 +05:30
2020-05-24 23:13:21 +05:30
### Git strategy
2016-08-24 12:49:21 +05:30
2020-04-22 19:07:51 +05:30
> - Introduced in GitLab 8.9 as an experimental feature.
> - `GIT_STRATEGY=none` requires GitLab Runner v1.7+.
2016-11-03 12:29:30 +05:30
You can set the `GIT_STRATEGY` used for getting recent application code, either
2018-05-09 12:01:36 +05:30
globally or per-job in the [`variables`](#variables) section. If left
2021-01-03 14:25:43 +05:30
unspecified, the default from the project settings is used.
2016-08-24 12:49:21 +05:30
2016-11-03 12:29:30 +05:30
There are three possible values: `clone`, `fetch`, and `none`.
`clone` is the slowest option. It clones the repository from scratch for every
2019-12-21 20:55:43 +05:30
job, ensuring that the local working copy is always pristine.
2016-08-24 12:49:21 +05:30
2017-08-17 22:00:37 +05:30
```yaml
2016-08-24 12:49:21 +05:30
variables:
GIT_STRATEGY: clone
```
2019-12-21 20:55:43 +05:30
`fetch` is faster as it re-uses the local working copy (falling back to `clone`
2020-05-24 23:13:21 +05:30
if it does not exist). `git clean` is used to undo any changes made by the last
2016-11-03 12:29:30 +05:30
job, and `git fetch` is used to retrieve commits made since the last job ran.
2016-08-24 12:49:21 +05:30
2017-08-17 22:00:37 +05:30
```yaml
2016-08-24 12:49:21 +05:30
variables:
GIT_STRATEGY: fetch
```
2021-01-03 14:25:43 +05:30
`none` also re-uses the local working copy. However, it skips all Git operations,
including GitLab Runner's pre-clone script, if present.
It's useful for jobs that operate exclusively on artifacts, like a deployment job.
Git repository data may be present, but it's likely out-of-date. You should only
2019-12-21 20:55:43 +05:30
rely on files brought into the local working copy from cache or artifacts.
2016-11-03 12:29:30 +05:30
2017-08-17 22:00:37 +05:30
```yaml
2016-11-03 12:29:30 +05:30
variables:
GIT_STRATEGY: none
```
2020-07-28 23:09:34 +05:30
NOTE: **Note:**
`GIT_STRATEGY` is not supported for
2019-03-02 22:35:43 +05:30
[Kubernetes executor](https://docs.gitlab.com/runner/executors/kubernetes.html),
2020-06-23 00:09:42 +05:30
but may be in the future. See the [support Git strategy with Kubernetes executor feature proposal](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3847)
2019-03-02 22:35:43 +05:30
for updates.
2020-05-24 23:13:21 +05:30
### Git submodule strategy
2017-08-17 22:00:37 +05:30
> Requires GitLab Runner v1.10+.
The `GIT_SUBMODULE_STRATEGY` variable is used to control if / how Git
2018-05-09 12:01:36 +05:30
submodules are included when fetching the code before a build. You can set them
globally or per-job in the [`variables`](#variables) section.
2017-08-17 22:00:37 +05:30
There are three possible values: `none`, `normal`, and `recursive`:
2021-01-03 14:25:43 +05:30
- `none` means that submodules are not included when fetching the project
2017-08-17 22:00:37 +05:30
code. This is the default, which matches the pre-v1.10 behavior.
2021-01-03 14:25:43 +05:30
- `normal` means that only the top-level submodules are included. It's
2017-08-17 22:00:37 +05:30
equivalent to:
2020-01-01 13:55:28 +05:30
```shell
2019-10-12 21:52:04 +05:30
git submodule sync
git submodule update --init
```
2017-08-17 22:00:37 +05:30
- `recursive` means that all submodules (including submodules of submodules)
2021-01-03 14:25:43 +05:30
are included. This feature needs Git v1.8.1 and later. When using a
2018-11-20 20:47:30 +05:30
GitLab Runner with an executor not based on Docker, make sure the Git version
2020-05-24 23:13:21 +05:30
meets that requirement. It's equivalent to:
2017-08-17 22:00:37 +05:30
2020-01-01 13:55:28 +05:30
```shell
2019-10-12 21:52:04 +05:30
git submodule sync --recursive
git submodule update --init --recursive
```
2017-08-17 22:00:37 +05:30
2021-01-03 14:25:43 +05:30
For this feature to work correctly, the submodules must be configured
2017-08-17 22:00:37 +05:30
(in `.gitmodules`) with either:
- the HTTP(S) URL of a publicly-accessible repository, or
- a relative path to another repository on the same GitLab server. See the
[Git submodules](../git_submodules.md) documentation.
2020-05-24 23:13:21 +05:30
### Git checkout
2018-05-09 12:01:36 +05:30
2019-07-07 11:18:12 +05:30
> Introduced in GitLab Runner 9.3.
2018-05-09 12:01:36 +05:30
The `GIT_CHECKOUT` variable can be used when the `GIT_STRATEGY` is set to either
`clone` or `fetch` to specify whether a `git checkout` should be run. If not
specified, it defaults to true. You can set them globally or per-job in the
[`variables`](#variables) section.
2021-01-03 14:25:43 +05:30
If set to `false`, the runner:
2018-05-09 12:01:36 +05:30
2021-01-03 14:25:43 +05:30
- when doing `fetch` - updates the repository and leaves the working copy on
2018-05-09 12:01:36 +05:30
the current revision,
2021-01-03 14:25:43 +05:30
- when doing `clone` - clones the repository and leaves the working copy on the
2018-05-09 12:01:36 +05:30
default branch.
2021-01-03 14:25:43 +05:30
If `GIT_CHECKOUT` is set to `true`, both `clone` and `fetch` work the same way.
The runner checks out the working copy of a revision related
2018-05-09 12:01:36 +05:30
to the CI pipeline:
```yaml
variables:
GIT_STRATEGY: clone
GIT_CHECKOUT: "false"
script:
2019-07-07 11:18:12 +05:30
- git checkout -B master origin/master
- git merge $CI_COMMIT_SHA
2018-05-09 12:01:36 +05:30
```
2017-08-17 22:00:37 +05:30
2020-05-24 23:13:21 +05:30
### Git clean flags
2019-07-07 11:18:12 +05:30
> Introduced in GitLab Runner 11.10
The `GIT_CLEAN_FLAGS` variable is used to control the default behavior of
`git clean` after checking out the sources. You can set it globally or per-job in the
[`variables`](#variables) section.
2019-12-21 20:55:43 +05:30
`GIT_CLEAN_FLAGS` accepts all possible options of the [`git clean`](https://git-scm.com/docs/git-clean)
2019-07-07 11:18:12 +05:30
command.
`git clean` is disabled if `GIT_CHECKOUT: "false"` is specified.
If `GIT_CLEAN_FLAGS` is:
- Not specified, `git clean` flags default to `-ffdx`.
- Given the value `none`, `git clean` is not executed.
For example:
```yaml
variables:
GIT_CLEAN_FLAGS: -ffdx -e cache/
script:
- ls -al cache/
```
2020-06-23 00:09:42 +05:30
### Git fetch extra flags
> [Introduced](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4142) in GitLab Runner 13.1.
The `GIT_FETCH_EXTRA_FLAGS` variable is used to control the behavior of
`git fetch`. You can set it globally or per-job in the [`variables`](#variables) section.
2021-01-03 14:25:43 +05:30
`GIT_FETCH_EXTRA_FLAGS` accepts all options of the [`git fetch`](https://git-scm.com/docs/git-fetch) command. However, `GIT_FETCH_EXTRA_FLAGS` flags are appended after the default flags that can't be modified.
2020-06-23 00:09:42 +05:30
The default flags are:
- [GIT_DEPTH](#shallow-cloning).
- The list of [refspecs](https://git-scm.com/book/en/v2/Git-Internals-The-Refspec).
- A remote called `origin`.
If `GIT_FETCH_EXTRA_FLAGS` is:
- Not specified, `git fetch` flags default to `--prune --quiet` along with the default flags.
- Given the value `none`, `git fetch` is executed only with the default flags.
For example, the default flags are `--prune --quiet`, so you can make `git fetch` more verbose by overriding this with just `--prune`:
```yaml
variables:
GIT_FETCH_EXTRA_FLAGS: --prune
script:
- ls -al cache/
```
2021-01-03 14:25:43 +05:30
The configuration above results in `git fetch` being called this way:
2020-06-23 00:09:42 +05:30
```shell
git fetch origin $REFSPECS --depth 50 --prune
```
2020-10-24 23:57:45 +05:30
Where `$REFSPECS` is a value provided to the runner internally by GitLab.
2020-06-23 00:09:42 +05:30
2020-05-24 23:13:21 +05:30
### Job stages attempts
2017-08-17 22:00:37 +05:30
> Introduced in GitLab, it requires GitLab Runner v1.9+.
2021-01-03 14:25:43 +05:30
You can set the number of attempts that the running job tries to execute
the following stages:
2017-08-17 22:00:37 +05:30
2020-10-24 23:57:45 +05:30
| Variable | Description |
|-----------------------------------|--------------------------------------------------------|
| **ARTIFACT_DOWNLOAD_ATTEMPTS** | Number of attempts to download artifacts running a job |
2021-01-03 14:25:43 +05:30
| **EXECUTOR_JOB_SECTION_ATTEMPTS** | [In GitLab 12.10](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4450) and later, the number of attempts to run a section in a job after a [`No Such Container`](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4450) error ([Docker executor](https://docs.gitlab.com/runner/executors/docker.html) only). |
2020-10-24 23:57:45 +05:30
| **GET_SOURCES_ATTEMPTS** | Number of attempts to fetch sources running a job |
| **RESTORE_CACHE_ATTEMPTS** | Number of attempts to restore the cache running a job |
2017-08-17 22:00:37 +05:30
The default is one single attempt.
Example:
```yaml
variables:
2017-09-10 17:25:29 +05:30
GET_SOURCES_ATTEMPTS: 3
2017-08-17 22:00:37 +05:30
```
2018-05-09 12:01:36 +05:30
You can set them globally or per-job in the [`variables`](#variables) section.
2017-08-17 22:00:37 +05:30
2021-01-03 14:25:43 +05:30
### Fallback cache key
> [Introduced](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/1534) in GitLab Runner 13.4.
You can use the `$CI_COMMIT_REF_SLUG` variable to specify your [`cache:key`](#cachekey).
For example, if your `$CI_COMMIT_REF_SLUG` is `test` you can set a job
to download cache that's tagged with `test`.
If a cache with this tag is not found, you can use `CACHE_FALLBACK_KEY` to
specify a cache to use when none exists.
For example:
```yaml
variables:
CACHE_FALLBACK_KEY: fallback-key
cache:
key: "$CI_COMMIT_REF_SLUG"
paths:
- binaries/
```
In this example, if the `$CI_COMMIT_REF_SLUG` is not found, the job uses the key defined
by the `CACHE_FALLBACK_KEY` variable.
2020-05-24 23:13:21 +05:30
### Shallow cloning
2016-08-24 12:49:21 +05:30
2020-04-22 19:07:51 +05:30
> Introduced in GitLab 8.9 as an experimental feature.
2021-01-03 14:25:43 +05:30
You can specify the depth of fetching and cloning using `GIT_DEPTH`.
`GIT_DEPTH` does a shallow clone of the repository and can significantly speed up cloning.
It can be helpful for repositories with a large number of commits or old, large binaries. The value is
2016-08-24 12:49:21 +05:30
passed to `git fetch` and `git clone`.
2021-01-03 14:25:43 +05:30
In GitLab 12.0 and later, newly-created projects automatically have a
[default `git depth` value of `50`](../pipelines/settings.md#git-shallow-clone).
If you use a depth of `1` and have a queue of jobs or retry
2017-08-17 22:00:37 +05:30
jobs, jobs may fail.
2016-08-24 12:49:21 +05:30
2021-01-03 14:25:43 +05:30
Git fetching and cloning is based on a ref, such as a branch name, so runners
can't clone a specific commit SHA. If multiple jobs are in the queue, or
you're retrying an old job, the commit to be tested must be within the
2017-08-17 22:00:37 +05:30
Git history that is cloned. Setting too small a value for `GIT_DEPTH` can make
2021-01-03 14:25:43 +05:30
it impossible to run these old commits and `unresolved reference` is displayed in
2017-08-17 22:00:37 +05:30
job logs. You should then reconsider changing `GIT_DEPTH` to a higher value.
2016-08-24 12:49:21 +05:30
2017-08-17 22:00:37 +05:30
Jobs that rely on `git describe` may not work correctly when `GIT_DEPTH` is
set since only part of the Git history is present.
2016-08-24 12:49:21 +05:30
To fetch or clone only the last 3 commits:
2017-08-17 22:00:37 +05:30
```yaml
2016-08-24 12:49:21 +05:30
variables:
GIT_DEPTH: "3"
```
2018-05-09 12:01:36 +05:30
You can set it globally or per-job in the [`variables`](#variables) section.
2020-05-24 23:13:21 +05:30
### Custom build directories
2019-07-07 11:18:12 +05:30
2020-10-24 23:57:45 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2211) in GitLab Runner 11.10.
2019-07-07 11:18:12 +05:30
2019-07-31 22:56:46 +05:30
By default, GitLab Runner clones the repository in a unique subpath of the
`$CI_BUILDS_DIR` directory. However, your project might require the code in a
specific directory (Go projects, for example). In that case, you can specify
2020-10-24 23:57:45 +05:30
the `GIT_CLONE_PATH` variable to tell the runner the directory to clone the
repository in:
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
```yaml
2019-07-07 11:18:12 +05:30
variables:
GIT_CLONE_PATH: $CI_BUILDS_DIR/project-name
test:
script:
- pwd
```
The `GIT_CLONE_PATH` has to always be within `$CI_BUILDS_DIR`. The directory set in `$CI_BUILDS_DIR`
is dependent on executor and configuration of [runners.builds_dir](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-section)
setting.
2021-01-03 14:25:43 +05:30
This can only be used when `custom_build_dir` is enabled in the
[runner's configuration](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscustom_build_dir-section).
This is the default configuration for the `docker` and `kubernetes` executors.
2020-05-24 23:13:21 +05:30
#### Handling concurrency
2019-07-07 11:18:12 +05:30
2021-01-03 14:25:43 +05:30
An executor that uses a concurrency greater than `1` might lead
to failures. Multiple jobs might be working on the same directory if the `builds_dir`
2019-07-07 11:18:12 +05:30
is shared between jobs.
2021-01-03 14:25:43 +05:30
The runner does not try to prevent this situation. It's up to the administrator
2020-10-24 23:57:45 +05:30
and developers to comply with the requirements of runner configuration.
2019-07-07 11:18:12 +05:30
2020-10-24 23:57:45 +05:30
To avoid this scenario, you can use a unique path within `$CI_BUILDS_DIR`, because runner
2019-07-07 11:18:12 +05:30
exposes two additional variables that provide a unique `ID` of concurrency:
- `$CI_CONCURRENT_ID`: Unique ID for all jobs running within the given executor.
- `$CI_CONCURRENT_PROJECT_ID`: Unique ID for all jobs running within the given executor and project.
The most stable configuration that should work well in any scenario and on any executor
is to use `$CI_CONCURRENT_ID` in the `GIT_CLONE_PATH`. For example:
2020-05-24 23:13:21 +05:30
```yaml
2019-07-07 11:18:12 +05:30
variables:
GIT_CLONE_PATH: $CI_BUILDS_DIR/$CI_CONCURRENT_ID/project-name
test:
script:
- pwd
```
The `$CI_CONCURRENT_PROJECT_ID` should be used in conjunction with `$CI_PROJECT_PATH`
as the `$CI_PROJECT_PATH` provides a path of a repository. That is, `group/subgroup/project`. For example:
2020-05-24 23:13:21 +05:30
```yaml
2019-07-07 11:18:12 +05:30
variables:
GIT_CLONE_PATH: $CI_BUILDS_DIR/$CI_CONCURRENT_ID/$CI_PROJECT_PATH
test:
script:
- pwd
```
2020-05-24 23:13:21 +05:30
#### Nested paths
2019-09-04 21:01:54 +05:30
The value of `GIT_CLONE_PATH` is expanded once and nesting variables
2020-05-24 23:13:21 +05:30
within is not supported.
2019-09-04 21:01:54 +05:30
For example, you define both the variables below in your
`.gitlab-ci.yml` file:
2020-05-24 23:13:21 +05:30
```yaml
2019-09-04 21:01:54 +05:30
variables:
GOPATH: $CI_BUILDS_DIR/go
GIT_CLONE_PATH: $GOPATH/src/namespace/project
```
The value of `GIT_CLONE_PATH` is expanded once into
`$CI_BUILDS_DIR/go/src/namespace/project`, and results in failure
2019-09-30 21:07:59 +05:30
because `$CI_BUILDS_DIR` is not expanded.
2019-09-04 21:01:54 +05:30
2018-05-09 12:01:36 +05:30
## Special YAML features
It's possible to use special YAML features like anchors (`&`), aliases (`*`)
2020-11-24 15:15:51 +05:30
and map merging (`<<`). Use these features to reduce the complexity
2018-05-09 12:01:36 +05:30
of `.gitlab-ci.yml`.
Read more about the various [YAML features](https://learnxinyminutes.com/docs/yaml/).
2020-07-28 23:09:34 +05:30
In most cases, the [`extends` keyword](#extends) is more user friendly and should
be used over these special YAML features. YAML anchors may still
need to be used to merge arrays.
2016-06-02 11:05:42 +05:30
### Anchors
2016-09-29 09:46:39 +05:30
> Introduced in GitLab 8.6 and GitLab Runner v1.1.1.
2016-06-02 11:05:42 +05:30
2021-01-03 14:25:43 +05:30
YAML has a feature called 'anchors' that you can use to duplicate
content across your document.
Use anchors to duplicate or inherit properties. Use anchors with [hidden jobs](#hide-jobs)
to provide templates for your jobs. When there are duplicate keys, GitLab
performs a reverse deep merge based on the keys.
You can't use YAML anchors across multiple files when leveraging the [`include`](#include)
feature. Anchors are only valid within the file they were defined in. Instead
of using YAML anchors, you can use the [`extends` keyword](#extends).
2016-06-02 11:05:42 +05:30
2021-01-03 14:25:43 +05:30
The following example uses anchors and map merging. It creates two jobs,
`test1` and `test2`, that inherit the parameters of `.job_template`, each
with their own custom `script` defined:
2016-06-02 11:05:42 +05:30
```yaml
2016-09-29 09:46:39 +05:30
.job_template: &job_definition # Hidden key that defines an anchor named 'job_definition'
2020-03-13 15:44:24 +05:30
image: ruby:2.6
2016-06-02 11:05:42 +05:30
services:
- postgres
- redis
test1:
<<: *job_definition # Merge the contents of the 'job_definition' alias
script:
- test1 project
test2:
<<: *job_definition # Merge the contents of the 'job_definition' alias
script:
- test2 project
```
`&` sets up the name of the anchor (`job_definition`), `<<` means "merge the
given hash into the current one", and `*` includes the named anchor
(`job_definition` again). The expanded version looks like this:
```yaml
.job_template:
2020-03-13 15:44:24 +05:30
image: ruby:2.6
2016-06-02 11:05:42 +05:30
services:
- postgres
- redis
test1:
2020-03-13 15:44:24 +05:30
image: ruby:2.6
2016-06-02 11:05:42 +05:30
services:
- postgres
- redis
script:
- test1 project
test2:
2020-03-13 15:44:24 +05:30
image: ruby:2.6
2016-06-02 11:05:42 +05:30
services:
- postgres
- redis
script:
- test2 project
```
2021-01-03 14:25:43 +05:30
Let's see another example. This time we use anchors to define two sets
of services. This configuration creates two jobs, `test:postgres` and `test:mysql`, that
share the `script` directive defined in `.job_template`, and the `services`
2016-06-02 11:05:42 +05:30
directive defined in `.postgres_services` and `.mysql_services` respectively:
```yaml
.job_template: &job_definition
script:
- test project
2020-07-28 23:09:34 +05:30
tags:
- dev
2016-06-02 11:05:42 +05:30
.postgres_services:
services: &postgres_definition
- postgres
- ruby
.mysql_services:
services: &mysql_definition
- mysql
- ruby
test:postgres:
2016-08-24 12:49:21 +05:30
<<: *job_definition
2016-06-02 11:05:42 +05:30
services: *postgres_definition
2020-07-28 23:09:34 +05:30
tags:
- postgres
2016-06-02 11:05:42 +05:30
test:mysql:
2016-08-24 12:49:21 +05:30
<<: *job_definition
2016-06-02 11:05:42 +05:30
services: *mysql_definition
```
The expanded version looks like this:
```yaml
.job_template:
script:
- test project
2020-07-28 23:09:34 +05:30
tags:
- dev
2016-06-02 11:05:42 +05:30
.postgres_services:
services:
- postgres
- ruby
.mysql_services:
services:
- mysql
- ruby
test:postgres:
script:
- test project
services:
- postgres
- ruby
2020-07-28 23:09:34 +05:30
tags:
- postgres
2016-06-02 11:05:42 +05:30
test:mysql:
script:
- test project
services:
- mysql
- ruby
2020-07-28 23:09:34 +05:30
tags:
- dev
2016-06-02 11:05:42 +05:30
```
2021-01-03 14:25:43 +05:30
You can see that the hidden jobs are conveniently used as templates, and
`tags: [dev]` has been overwritten by `tags: [postgres]`.
2020-01-01 13:55:28 +05:30
2020-03-13 15:44:24 +05:30
#### YAML anchors for `before_script` and `after_script`
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/23005) in GitLab 12.5.
2020-03-13 15:44:24 +05:30
You can use [YAML anchors](#anchors) with `before_script` and `after_script`,
which makes it possible to include a predefined list of commands in multiple
jobs.
Example:
```yaml
.something_before: &something_before
2020-07-28 23:09:34 +05:30
- echo 'something before'
2020-03-13 15:44:24 +05:30
.something_after: &something_after
2020-07-28 23:09:34 +05:30
- echo 'something after'
- echo 'another thing after'
2020-03-13 15:44:24 +05:30
job_name:
before_script:
- *something_before
script:
- echo 'this is the script'
after_script:
- *something_after
```
#### YAML anchors for `script`
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/23005) in GitLab 12.5.
2020-03-13 15:44:24 +05:30
You can use [YAML anchors](#anchors) with scripts, which makes it possible to
include a predefined list of commands in multiple jobs.
For example:
```yaml
.something: &something
2020-07-28 23:09:34 +05:30
- echo 'something'
2020-03-13 15:44:24 +05:30
job_name:
script:
- *something
- echo 'this is the script'
```
#### YAML anchors for variables
[YAML anchors](#anchors) can be used with `variables`, to easily repeat assignment
of variables across multiple jobs. It can also enable more flexibility when a job
requires a specific `variables` block that would otherwise override the global variables.
2021-01-03 14:25:43 +05:30
In the example below, we override the `GIT_STRATEGY` variable without affecting
2020-03-13 15:44:24 +05:30
the use of the `SAMPLE_VARIABLE` variable:
```yaml
# global variables
variables: &global-variables
SAMPLE_VARIABLE: sample_variable_value
2020-06-23 00:09:42 +05:30
ANOTHER_SAMPLE_VARIABLE: another_sample_variable_value
2020-03-13 15:44:24 +05:30
2021-01-03 14:25:43 +05:30
# a job that must set the GIT_STRATEGY variable, yet depend on global variables
2020-03-13 15:44:24 +05:30
job_no_git_strategy:
stage: cleanup
variables:
<<: *global-variables
GIT_STRATEGY: none
script: echo $SAMPLE_VARIABLE
```
2020-05-24 23:13:21 +05:30
### Hide jobs
2016-09-29 09:46:39 +05:30
2020-05-24 23:13:21 +05:30
> Introduced in GitLab 8.6 and GitLab Runner v1.1.1.
2019-07-07 11:18:12 +05:30
2020-05-24 23:13:21 +05:30
If you want to temporarily 'disable' a job, rather than commenting out all the
lines where the job is defined:
2016-09-29 09:46:39 +05:30
2020-05-24 23:13:21 +05:30
```yaml
2020-11-24 15:15:51 +05:30
# hidden_job:
# script:
# - run test
2020-05-24 23:13:21 +05:30
```
2021-01-03 14:25:43 +05:30
Instead, you can start its name with a dot (`.`) and it is not processed by
GitLab CI/CD. In the following example, `.hidden_job` is ignored:
2020-05-24 23:13:21 +05:30
```yaml
.hidden_job:
script:
- run test
```
Use this feature to ignore jobs, or use the
[special YAML features](#special-yaml-features) and transform the hidden jobs
into templates.
## Skip Pipeline
If your commit message contains `[ci skip]` or `[skip ci]`, using any
2021-01-03 14:25:43 +05:30
capitalization, the commit is created but the pipeline is skipped.
2020-05-24 23:13:21 +05:30
Alternatively, one can pass the `ci.skip` [Git push option](../../user/project/push_options.md#push-options-for-gitlab-cicd)
if using Git 2.10 or newer.
2015-11-26 14:37:03 +05:30
2019-07-07 11:18:12 +05:30
## Processing Git pushes
2021-01-03 14:25:43 +05:30
GitLab creates at most four branch and tag pipelines when
pushing multiple changes in a single `git push` invocation.
2019-07-07 11:18:12 +05:30
2021-01-03 14:25:43 +05:30
This limitation does not affect any of the updated merge request pipelines.
All updated merge requests have a pipeline created when using
2019-07-07 11:18:12 +05:30
[pipelines for merge requests](../merge_request_pipelines/index.md).
2020-05-24 23:13:21 +05:30
## Deprecated parameters
2017-08-17 22:00:37 +05:30
2020-05-24 23:13:21 +05:30
The following parameters are deprecated.
2017-08-17 22:00:37 +05:30
2020-05-24 23:13:21 +05:30
### Globally-defined `types`
CAUTION: **Deprecated:**
`types` is deprecated, and could be removed in a future release.
Use [`stages`](#stages) instead.
### Job-defined `type`
CAUTION: **Deprecated:**
`type` is deprecated, and could be removed in one of the future releases.
Use [`stage`](#stage) instead.
### Globally-defined `image`, `services`, `cache`, `before_script`, `after_script`
Defining `image`, `services`, `cache`, `before_script`, and
`after_script` globally is deprecated. Support could be removed
from a future release.
Use [`default:`](#global-defaults) instead. For example:
```yaml
default:
image: ruby:2.5
services:
- docker:dind
cache:
paths: [vendor/]
before_script:
- bundle install --path vendor/
after_script:
- rm -rf tmp/
```
2019-02-15 15:39:39 +05:30
2019-09-04 21:01:54 +05:30
<!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
one might have when setting this up, or when something is changed, or on upgrading, it's
important to describe those, too. Think of things that may go wrong and include them here.
This is important to minimize requests for support, and to avoid doc comments with
questions that you know someone might ask.
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. -->