diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-27 12:08:30 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-27 12:08:30 +0300 |
| commit | 7892ed2e23152070d626f583888eb24a3b801c0e (patch) | |
| tree | afaf4812551be70e3974d1e6b4c2c20191c9b72c /doc/ci/quick_start | |
| parent | 5c763ac4c62bdeb0f0fe26f710c0a7a91921a949 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/quick_start')
| -rw-r--r-- | doc/ci/quick_start/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/quick_start/README.md b/doc/ci/quick_start/README.md index a14cfcfa9ed..a75fd775872 100644 --- a/doc/ci/quick_start/README.md +++ b/doc/ci/quick_start/README.md @@ -165,7 +165,7 @@ The next step is to configure a Runner so that it picks the pending jobs. ## Configuring a Runner In GitLab, Runners run the jobs that you define in `.gitlab-ci.yml`. A Runner -can be a virtual machine, a VPS, a bare-metal machine, a docker container or +can be a virtual machine, a VPS, a bare-metal machine, a Docker container or even a cluster of containers. GitLab and the Runners communicate through an API, so the only requirement is that the Runner's machine has network access to the GitLab server. |