diff options
| author | Filip Krakowski <Filip.Krakowski@Uni-Duesseldorf.de> | 2017-06-01 11:58:34 +0200 |
|---|---|---|
| committer | Shinya Maeda <gitlab.shinyamaeda@gmail.com> | 2017-06-08 00:34:58 +0900 |
| commit | 6c8e72b4108e5c671970a3965b214c8b1dda53ae (patch) | |
| tree | 20ffdbf25e88bb1065f83039385accb78671e2d8 /doc/ci | |
| parent | 0601ac5d0b0330fb21228bef82650b3d3f6898cb (diff) | |
| download | gitlab-ce-6c8e72b4108e5c671970a3965b214c8b1dda53ae.tar.gz | |
Add 'schedules' keyword to 'only' and 'except'
Diffstat (limited to 'doc/ci')
| -rw-r--r-- | doc/ci/yaml/README.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md index fc813694ff2..7c085bf77c9 100644 --- a/doc/ci/yaml/README.md +++ b/doc/ci/yaml/README.md @@ -393,7 +393,7 @@ There are a few rules that apply to the usage of refs policy: * `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. -* `only` and `except` allow the use of special keywords: `branches`, `tags`, and `triggers`. +* `only` and `except` allow the use of special keywords: `branches`, `tags`, `triggers` and `schedules`. * `only` and `except` allow to specify a repository path to filter jobs for forks. @@ -411,7 +411,7 @@ job: ``` In this example, `job` will run only for refs that are tagged, or if a build is -explicitly requested via an API trigger. +explicitly requested via an API trigger or a Pipeline Schedule. ```yaml job: @@ -419,6 +419,7 @@ job: only: - tags - triggers + - schedules ``` The repository path can be used to have jobs executed only for the parent |