diff options
| author | Z.J. van de Weg <git@zjvandeweg.nl> | 2017-05-10 10:04:25 +0200 |
|---|---|---|
| committer | Z.J. van de Weg <git@zjvandeweg.nl> | 2017-05-15 10:01:29 +0200 |
| commit | 9f933953896d4a1ca7ee40ce3fef4ead4b73ab65 (patch) | |
| tree | 0cff70f3863105fb0b958828790b5557cf9b27d8 /doc | |
| parent | e261b4b8517ba6d5d5b082f1955836c945fd51fc (diff) | |
| download | gitlab-ce-9f933953896d4a1ca7ee40ce3fef4ead4b73ab65.tar.gz | |
Do not schedule pipelines if the user can't
When the owner of a pipelines schedule was either blocked or was removed
from the project, the pipeline schedular would still schedule the
pipeline.
This would than fail however, given the user had no access to the
project and it contents. However, a better way to handle it would be to
not schedule it at all. Furthermore, from now on, such schedules will be
deactivated so the schedule worker can ignore it on the next runs.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ci/pipeline_schedules.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/ci/pipeline_schedules.md b/doc/ci/pipeline_schedules.md index 0a9b0e7173f..73451da6c0c 100644 --- a/doc/ci/pipeline_schedules.md +++ b/doc/ci/pipeline_schedules.md @@ -35,6 +35,10 @@ To change the Sidekiq worker's frequency, you have to edit the `trigger_schedule value in your `gitlab.rb` and restart GitLab. The Sidekiq worker's configuration on GiLab.com is able to be looked up at [here](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example#L185). - Cron notation is parsed by [Rufus-Scheduler](https://github.com/jmettraux/rufus-scheduler). +- When the owner of the schedule does not have the ability to create pipelines +anymore, due to e.g. being blocked or removed from the project, the schedule is +deactivated. Another user can take ownership and activate it, so the schedule is +run again. [ce-10533]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10533 [ce-10853]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10853 |