summaryrefslogtreecommitdiff
path: root/doc/ci/chatops
diff options
context:
space:
mode:
authorMarcel Amirault <ravlen@gmail.com>2019-03-11 05:45:02 +0000
committerEvan Read <eread@gitlab.com>2019-03-11 05:45:02 +0000
commit4c623955d978ee7c7ee5d2370682aabfe593e0ff (patch)
treecae68ca731467395114592019bf577b15c633acd /doc/ci/chatops
parent0ccb31de234f937fcdb27faccfce4a595495b7c6 (diff)
downloadgitlab-ce-4c623955d978ee7c7ee5d2370682aabfe593e0ff.tar.gz
Docs: Fix markdown for link in chatops doc
Diffstat (limited to 'doc/ci/chatops')
-rw-r--r--doc/ci/chatops/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/chatops/README.md b/doc/ci/chatops/README.md
index 6ad1df7bb2a..df7fb8a4912 100644
--- a/doc/ci/chatops/README.md
+++ b/doc/ci/chatops/README.md
@@ -12,7 +12,7 @@ GitLab ChatOps provides a method to interact with CI/CD jobs through chat servic
GitLab ChatOps is built upon two existing features, [GitLab CI/CD](../README.md) and [Slack Slash Commmands](../../user/project/integrations/slack_slash_commands.md).
-A new `run` action has been added to the [slash commands](../../integration/slash_commands.md), which takes two arguments: a `<job name>` to execute and the `<job arguments>`. When executed, ChatOps will look up the specified job name and attempt to match it to a corresponding job in [.gitlab-ci.yml](../yaml/README.md). If a matching job is found on `master`, a pipeline containing just that job is scheduled. Two additional [CI/CD variables](../variables/README.html#predefined-variables-environment-variables) are passed to the job: `CHAT_INPUT` contains any additional arguments, and `CHAT_CHANNEL` is set to the name of channel the action was triggered in.
+A new `run` action has been added to the [slash commands](../../integration/slash_commands.md), which takes two arguments: a `<job name>` to execute and the `<job arguments>`. When executed, ChatOps will look up the specified job name and attempt to match it to a corresponding job in [.gitlab-ci.yml](../yaml/README.md). If a matching job is found on `master`, a pipeline containing just that job is scheduled. Two additional [CI/CD variables](../variables/README.md#predefined-environment-variables) are passed to the job: `CHAT_INPUT` contains any additional arguments, and `CHAT_CHANNEL` is set to the name of channel the action was triggered in.
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.