summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorElan Ruusamäe <glen@delfi.ee>2017-06-12 07:16:38 +0000
committerGrzegorz Bizon <grzegorz@gitlab.com>2017-06-12 07:16:38 +0000
commitfe1f69442ce12a36987067f67ff0b9f33260af21 (patch)
treeb75ed470e3c6d0a01e7d22944f6d1d5bedc42d6b
parent1e3bb74d4d4fe036ff54f3039b454b0f3a0de8ec (diff)
downloadgitlab-ce-fe1f69442ce12a36987067f67ff0b9f33260af21.tar.gz
doc: add example of scheduler when
-rw-r--r--doc/user/project/pipelines/schedules.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/user/project/pipelines/schedules.md b/doc/user/project/pipelines/schedules.md
index d19d184f9b0..17cc21238ff 100644
--- a/doc/user/project/pipelines/schedules.md
+++ b/doc/user/project/pipelines/schedules.md
@@ -31,6 +31,26 @@ is installed on.
![Schedules list](img/pipeline_schedules_list.png)
+## Using only and except
+
+To configure that a job can be executed only when the pipeline has been
+scheduled (or the opposite), you can use
+[only and except](../../../ci/yaml/README.md#only-and-except) configuration keywords.
+
+```
+job:on-schedule:
+ only:
+ - schedules
+ script:
+ - make world
+
+job:
+ except:
+ - schedules
+ script:
+ - make build
+```
+
## Taking ownership
Pipelines are executed as a user, who owns a schedule. This influences what