1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
---
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/#assignments
---
# How to configure GitLab Runner for GitLab CE integration tests
We will register the runner using a confined Docker executor.
The registration token can be found at `https://gitlab.com/project_namespace/project_name/runners`.
You can export it as a variable and run the commands below as-is. Start by
creating a template configuration file in order to pass complex configuration:
```shell
$ cat > /tmp/test-config.template.toml << EOF
[[runners]]
[runners.docker]
[[runners.docker.services]]
name = "mysql:latest"
[[runners.docker.services]]
name = "redis:latest"
EOF
```
Finally, register the runner, passing the newly created template configuration file:
```shell
gitlab-runner register \
--non-interactive \
--url "https://gitlab.com" \
--registration-token "$REGISTRATION_TOKEN" \
--template-config /tmp/test-config.template.toml \
--description "gitlab-ce-ruby-2.7" \
--executor "docker" \
--docker-image ruby:2.7
```
You now have a GitLab CE integration testing instance with bundle caching.
Push some commits to test it.
For [advanced configuration](../configuration/advanced-configuration.md), look into
`/etc/gitlab-runner/config.toml` and tune it.
|
