summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axilleas@axilleas.me>2016-04-11 12:41:27 +0300
committerAchilleas Pipinellis <axilleas@axilleas.me>2016-04-11 12:41:27 +0300
commitd86190eead0075d1b0ba7e73ff2efa8a610b5398 (patch)
treea57aa05fe026b14d40842c6968498edc544c97ba
parent3122e5cc847b224d5531f23a9c2fe9bc2043b01f (diff)
downloadgitlab-ce-docs/notice-about-gitlab-runner.tar.gz
Add a note about installing Runners in ci/runners/README.mddocs/notice-about-gitlab-runner
-rw-r--r--doc/ci/runners/README.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/ci/runners/README.md b/doc/ci/runners/README.md
index 295d953db11..36e90e21419 100644
--- a/doc/ci/runners/README.md
+++ b/doc/ci/runners/README.md
@@ -7,6 +7,10 @@ through the coordinator API of GitLab CI.
A runner can be specific to a certain project or serve any project
in GitLab CI. A runner that serves all projects is called a shared runner.
+Ideally, GitLab Runner should not be installed on the same machine as GitLab.
+Read the [requirements documentation](../../install/requirements.md#gitlab-runner)
+for more information.
+
## Shared vs. Specific Runners
A runner that is specific only runs for the specified project. A shared runner
@@ -140,7 +144,7 @@ to it. This means that if you have shared runners setup for a project and
someone forks that project, the shared runners will also serve jobs of this
project.
-# Attack vectors in runners
+## Attack vectors in Runners
Mentioned briefly earlier, but the following things of runners can be exploited.
We're always looking for contributions that can mitigate these [Security Considerations](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/security/index.md).