diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-30 03:09:09 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-30 03:09:09 +0300 |
| commit | c36e59283ebcfd75281a9dda227ed060eeb5fbe7 (patch) | |
| tree | 282c293bb93f3fc7798485b2410c47fdbf2cd50a /doc/ci/chatops | |
| parent | 27d314277bfe7fffec215efa9b1833a23bb82940 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/chatops')
| -rw-r--r-- | doc/ci/chatops/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/chatops/README.md b/doc/ci/chatops/README.md index ec3d13e7500..799ace903b2 100644 --- a/doc/ci/chatops/README.md +++ b/doc/ci/chatops/README.md @@ -23,7 +23,7 @@ A new `run` action has been added to the [slash commands](../../integration/slas After the job has finished, its output is sent back to Slack provided it has completed within 30 minutes. If a job takes more than 30 minutes to run it must use the Slack API to manually send data back to a channel. -[Developer access and above](../../user/permissions.html#project-members-permissions) is required to use the `run` command. If a job should not be able to be triggered from chat, it can be set to `except: [chat]`. +[Developer access and above](../../user/permissions.md#project-members-permissions) is required to use the `run` command. If a job should not be able to be triggered from chat, it can be set to `except: [chat]`. ## Creating a ChatOps CI job @@ -31,7 +31,7 @@ Since ChatOps is built upon GitLab CI/CD, the job has all the same features and - It is strongly recommended to set `only: [chat]` so the job does not run as part of the standard CI pipeline. - If the job is set to `when: manual`, the pipeline will be created however the job will wait to be started. -- It is important to keep in mind that there is limited support for access control. If the user who triggered the slash command is a developer in the project, the job will run. The job itself can utilize existing [CI/CD variables](../variables/README.html#predefined-environment-variables) like `GITLAB_USER_ID` to perform additional rights validation, however these variables can be [overridden](../variables/README.html#priority-of-environment-variables). +- It is important to keep in mind that there is limited support for access control. If the user who triggered the slash command is a developer in the project, the job will run. The job itself can utilize existing [CI/CD variables](../variables/README.md#predefined-environment-variables) like `GITLAB_USER_ID` to perform additional rights validation, however these variables can be [overridden](../variables/README.md#priority-of-environment-variables). ### Controlling the ChatOps reply |