summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcia Ramos <virtua.creative@gmail.com>2019-05-27 20:41:10 +0100
committerMarcia Ramos <virtua.creative@gmail.com>2019-05-27 20:41:10 +0100
commit4890efc9d4d83172b421e4874d63b47684da8745 (patch)
treef53806a5a24974d2d44ff63a85a5ec0367cf0286
parent894d34b3c2b766fdf9254bab5ae6425142c282da (diff)
downloadgitlab-ce-docs-ssot-ci-services.tar.gz
Improve description, add doc typedocs-ssot-ci-services
-rw-r--r--doc/ci/services/README.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/ci/services/README.md b/doc/ci/services/README.md
index 2eda5d23976..7fe12eb53e7 100644
--- a/doc/ci/services/README.md
+++ b/doc/ci/services/README.md
@@ -1,13 +1,18 @@
---
comments: false
+type: index
---
-# GitLab CI Services
+# GitLab CI services examples
-GitLab CI uses the `services` keyword to define what docker containers should
-be linked with your base image. Below is a list of examples you may use.
+The [`services`](../docker/using_docker_images.md#what-is-a-service)
+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.
+
+The service image can run any application, but the most common use
+case is to run a database container, for example:
- [Using MySQL](mysql.md)
- [Using PostgreSQL](postgres.md)
- [Using Redis](redis.md)
-- [Using Other Services](../docker/using_docker_images.md#what-is-a-service)