diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-08 21:09:32 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-08 21:09:32 +0300 |
| commit | 7e17b031fa8e57a698fc474ded12eaa2553c87f5 (patch) | |
| tree | d753ae5527f835901f86a30608c024e86e11fbaa /doc/ci/chatops | |
| parent | 66a3180a3b9417cb5259ecca83934f22b136394b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/chatops')
| -rw-r--r-- | doc/ci/chatops/index.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/chatops/index.md b/doc/ci/chatops/index.md index c277d12cb49..54f48d7bbee 100644 --- a/doc/ci/chatops/index.md +++ b/doc/ci/chatops/index.md @@ -40,8 +40,8 @@ job completes: - If the job completes in *more than 30 minutes*, the job must use the [Slack API](https://api.slack.com/) to send data to the channel. -To use the `run` command, you must have -[Developer access or above](../../user/permissions.md#project-members-permissions). +To use the `run` command, you must have the +[Developer role or higher](../../user/permissions.md#project-members-permissions). If a job shouldn't be able to be triggered from chat, you can set the job to `except: [chat]`. ## Best practices for ChatOps CI jobs @@ -53,7 +53,7 @@ functions available. Consider these best practices when creating ChatOps jobs: of the standard CI pipeline. - If the job is set to `when: manual`, ChatOps creates the pipeline, but the job waits to be started. - ChatOps provides limited support for access control. If the user triggering the - slash command has [Developer access or above](../../user/permissions.md#project-members-permissions) + slash command has the [Developer role or higher](../../user/permissions.md#project-members-permissions) in the project, the job runs. The job itself can use existing [CI/CD variables](../variables/index.md#predefined-cicd-variables) like `GITLAB_USER_ID` to perform additional rights validation, but |