summaryrefslogtreecommitdiff
path: root/doc/ci/services
diff options
context:
space:
mode:
Diffstat (limited to 'doc/ci/services')
-rw-r--r--doc/ci/services/README.md3
-rw-r--r--doc/ci/services/mysql.md5
-rw-r--r--doc/ci/services/postgres.md5
-rw-r--r--doc/ci/services/redis.md5
4 files changed, 15 insertions, 3 deletions
diff --git a/doc/ci/services/README.md b/doc/ci/services/README.md
index 7fe12eb53e7..fda453b7aa0 100644
--- a/doc/ci/services/README.md
+++ b/doc/ci/services/README.md
@@ -1,4 +1,7 @@
---
+stage: Verify
+group: Runner
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
comments: false
type: index
---
diff --git a/doc/ci/services/mysql.md b/doc/ci/services/mysql.md
index dcfd863709e..1b017111d22 100644
--- a/doc/ci/services/mysql.md
+++ b/doc/ci/services/mysql.md
@@ -1,4 +1,7 @@
---
+stage: Verify
+group: Runner
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
type: reference
---
@@ -43,7 +46,7 @@ Database: <your_mysql_database>
If you are wondering why we used `mysql` for the `Host`, read more at
[How services are linked to the job](../docker/using_docker_images.md#how-services-are-linked-to-the-job).
-You can also use any other docker image available on [Docker Hub](https://hub.docker.com/_/mysql/).
+You can also use any other Docker image available on [Docker Hub](https://hub.docker.com/_/mysql/).
For example, to use MySQL 5.5 the service becomes `mysql:5.5`.
The `mysql` image can accept some environment variables. For more details
diff --git a/doc/ci/services/postgres.md b/doc/ci/services/postgres.md
index 2f92bd969ff..aadbce5a50a 100644
--- a/doc/ci/services/postgres.md
+++ b/doc/ci/services/postgres.md
@@ -1,4 +1,7 @@
---
+stage: Verify
+group: Runner
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
type: reference
---
@@ -45,7 +48,7 @@ Database: nice_marmot
If you are wondering why we used `postgres` for the `Host`, read more at
[How services are linked to the job](../docker/using_docker_images.md#how-services-are-linked-to-the-job).
-You can also use any other docker image available on [Docker Hub](https://hub.docker.com/_/postgres).
+You can also use any other Docker image available on [Docker Hub](https://hub.docker.com/_/postgres).
For example, to use PostgreSQL 9.3 the service becomes `postgres:9.3`.
The `postgres` image can accept some environment variables. For more details
diff --git a/doc/ci/services/redis.md b/doc/ci/services/redis.md
index f22ee87a9d3..193f78f240b 100644
--- a/doc/ci/services/redis.md
+++ b/doc/ci/services/redis.md
@@ -1,4 +1,7 @@
---
+stage: Verify
+group: Runner
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
type: reference
---
@@ -30,7 +33,7 @@ Host: redis
And that's it. Redis will now be available to be used within your testing
framework.
-You can also use any other docker image available on [Docker Hub](https://hub.docker.com/_/redis).
+You can also use any other Docker image available on [Docker Hub](https://hub.docker.com/_/redis).
For example, to use Redis 2.8 the service becomes `redis:2.8`.
## Use Redis with the Shell executor