| ... | ... | @@ -229,6 +229,12 @@ 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.
|
|
|
|
|
|
|
|
### Troubleshooting gitlab runners
|
|
|
|
|
|
|
|
If you have any issue with gitlab runner (for example, an online runner but no debug logs) during your pipeline execution,
|
|
|
|
the following [official documentation](https://docs.gitlab.com/runner/faq/) may help you.
|
|
|
|
For example, it may show you how to enable debug logging on your runner.
|
|
|
|
|
|
|
|
### 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, see https://stackoverflow.com/questions/49998099/dns-not-working-within-docker-containers-when-host-uses-dnsmasq-and-googles-dns). This can be solved by adding `network_mode = "host"` in the configuration. Eg. `/etc/gitlab-runner/config.toml`:
|
| ... | ... | |
