summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Winata <awinata@gitlab.com>2019-02-21 05:12:09 +0000
committerEvan Read <eread@gitlab.com>2019-05-28 13:17:17 +1000
commitaaaf0f737ee15ef079a16bdb3341aeabee1ef8e4 (patch)
treec88a533c27d4e0ba8ee41d596d1c95d7bbbe4910
parent24befd5450f78b6111b32616cabfad4e50bbfd36 (diff)
downloadgitlab-ce-aaaf0f737ee15ef079a16bdb3341aeabee1ef8e4.tar.gz
Mentioned executors type
Also another factor of consideration for runner server requirements.
-rw-r--r--doc/install/requirements.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index ba2f46f32b4..adaceda383f 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -209,7 +209,7 @@ We recommend using a separate machine for each GitLab Runner, if you plan to
use the CI features.
The server requirements for your GitLab runner depends on resources required to
-run the build jobs as well as the number of job concurrency you configured on
+run the build jobs as well as the number of job concurrency and the executors you configured on
GitLab runner. Since the nature of the jobs varies for each use case, you will
need to experiment by adjusting the job concurrency to get the optimum number.