summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorvalentin bancarel <bancarel.valentin@gmail.com>2019-03-06 13:10:56 +0000
committerSteve Azzopardi <steveazz@outlook.com>2019-03-08 11:16:10 +0100
commitfae18a049008119e19590ee8331bc2fbb9b8a9d7 (patch)
tree2f5c0fc80943c599901c7637a717677d6dd1b06d
parentb4852ab49a385f3cc900cf0f2584097b8a154ac0 (diff)
downloadgitlab-ce-fae18a049008119e19590ee8331bc2fbb9b8a9d7.tar.gz
Update README.md
-rw-r--r--doc/ci/yaml/README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md
index 985895acce3..f170323059a 100644
--- a/doc/ci/yaml/README.md
+++ b/doc/ci/yaml/README.md
@@ -268,6 +268,12 @@ There are also two edge cases worth mentioning:
### `stage`
+NOTE: **Note:**
+By default, when using your own Runners, the GitLab Runner installation is set up to run only one job at a time (see the `concurrent` flag in [Runner global settings](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section) for more information).
+Jobs will run in parallel only if:
+ - Run on different Runners
+ - The Runner's `concurrent` config has been changed.
+
`stage` is defined per-job and relies on [`stages`](#stages) which is defined
globally. It allows to group jobs into different stages, and jobs of the same
`stage` are executed in `parallel`. For example: