Configuring GitLab Runner

Below you can find some specific documentation on configuring GitLab Runner, the shells supported, the security implications using the various executors, as well as information how to set up Prometheus metrics:

• Advanced configuration options Learn how to use the TOML configuration file that GitLab Runner uses.
• Use self-signed certificates Configure certificates that are used to verify TLS peer when connecting to the GitLab server.
• Autoscaling using Docker machine Execute jobs on machines that are created on demand using Docker machine.
• Autoscaling GitLab Runner on AWS EC2
• Autoscaling GitLab CI on AWS Fargate Learn how to configure the Runner and the AWS Fargate driver with the Runner Custom executor.
• The init system of GitLab Runner Learn how the Runner installs its init service files based on your operating system.
• Supported shells Learn what shell script generators are supported that allow to execute builds on different systems.
• Security considerations Be aware of potential security implications when running your jobs with GitLab Runner.
• Runner monitoring Learn how to monitor the Runner’s behavior.
• Cleanup the Docker images automatically A simple Docker application that automatically garbage collects the GitLab Runner caches and images when running low on disk space.
• Configure GitLab Runner to run behind a proxy Learn how to set up a Linux proxy and configure GitLab Runner. Especially useful for the Docker executor.
• Best practice for using GitLab Runner.
• Handling rate limited requests