... | ... | @@ -107,7 +107,7 @@ becomes clear when the "gitlab-ci tag" concept is understood. |
|
|
When asked
|
|
|
|
|
|
Please enter the executor:
|
|
|
you should answer `shell`
|
|
|
you should answer `shell` (or `docker` but then see the related subsection below)
|
|
|
|
|
|
At the end of this step, your runner should appear in the *Settings > Pipelines* tab of your project.
|
|
|
|
... | ... | @@ -117,6 +117,27 @@ At the end of this step, your runner should appear in the *Settings > Pipelines* |
|
|
Finally, configure the tasks to run by creating a .gitlab-ci.yml file at the root of your project.
|
|
|
Follow the official documentation at <https://docs.gitlab.com/ce/ci/yaml/> to create this file.
|
|
|
|
|
|
### Using a docker executor
|
|
|
|
|
|
It has been reported that there are DNS issues with docker running on the INRIA CI's VMs (due to bad interaction between dnsmasq and docker). This can be solved by adding `network_mode = "host"` in the configuration. Eg. `/etc/gitlab-runner/config.toml`:
|
|
|
|
|
|
concurrent = 1
|
|
|
check_interval = 0
|
|
|
|
|
|
[[runners]]
|
|
|
name = "ci.inria"
|
|
|
url = " [ https://gitlab.inria.fr/ | https://gitlab.inria.fr/ ] "
|
|
|
token = "..."
|
|
|
executor = "docker"
|
|
|
[runners.docker]
|
|
|
network_mode = "host"
|
|
|
tls_verify = false
|
|
|
image = "alpine:latest"
|
|
|
privileged = false
|
|
|
disable_cache = false
|
|
|
volumes = ["/cache"]
|
|
|
shm_size = 0
|
|
|
[runners.cache]
|
|
|
|
|
|
## Git-LFS is not activated
|
|
|
|
... | ... | |