Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2022-08-31 03:12:33 +0300
committerGitLab Bot <gitlab-bot@gitlab.com>2022-08-31 03:12:33 +0300
commitf97832e536bf561a20b81c07e35884454691dcf8 (patch)
tree803e0e0ec48901a042e9eb95930acb357698cddb /doc/ci/services
parent6377fb774cd6bf76ea235c9e07d88cdb014ee1ad (diff)
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/services')
-rw-r--r--doc/ci/services/index.md9
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/ci/services/index.md b/doc/ci/services/index.md
index ba3f806c96e..9b2bcc39b3e 100644
--- a/doc/ci/services/index.md
+++ b/doc/ci/services/index.md
@@ -8,9 +8,12 @@ type: index
# Services **(FREE)**
-The `services` keyword defines a Docker image that runs during a `job`
-linked to the Docker image that the image keyword defines. This allows
-you to access the service image during build time.
+When you configure CI/CD, you specify an image, which is used to create the container
+where your jobs will run. To specify this image, you use the `image` keyword.
+
+You can specify an additional image by using the `services` keyword. This additional
+image is used to create another container, which is available to the first container.
+The two containers have access to one another and can communicate when running the job.
The service image can run any application, but the most common use
case is to run a database container, for example: