diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-14 21:08:47 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-14 21:08:47 +0300 |
| commit | 93960490b8bdbc0f2ab1d102b83ec5d5b87c97a6 (patch) | |
| tree | 05e12b8fc3094f8de548aff4f929ef3433a3f52e /doc/ci/triggers | |
| parent | 99670fc6a027caee34a6537c8def2e998d1ac5c2 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/triggers')
| -rw-r--r-- | doc/ci/triggers/README.md | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/ci/triggers/README.md b/doc/ci/triggers/README.md index 1b01855bbc7..bcd19f0de6f 100644 --- a/doc/ci/triggers/README.md +++ b/doc/ci/triggers/README.md @@ -252,10 +252,6 @@ of all types of variables. ## Using cron to trigger nightly pipelines -NOTE: **Note:** -The following behavior can also be achieved through GitLab's UI with -[pipeline schedules](../pipelines/schedules.md). - Whether you craft a script or just run cURL directly, you can trigger jobs in conjunction with cron. The example below triggers a job on the `master` branch of project with ID `9` every night at `00:30`: @@ -264,6 +260,9 @@ branch of project with ID `9` every night at `00:30`: 30 0 * * * curl --request POST --form token=TOKEN --form ref=master https://gitlab.example.com/api/v4/projects/9/trigger/pipeline ``` +This behavior can also be achieved through GitLab's UI with +[pipeline schedules](../pipelines/schedules.md). + ## Legacy triggers Old triggers, created before GitLab 9.0 are marked as legacy. |