Configure GitLab Runner
Tier: Free, Premium, Ultimate
Offering: SaaS, self-managed
Offering: SaaS, self-managed
Learn how to configure GitLab Runner.
-
Advanced configuration options: Use
the
config.tomlconfiguration file to edit runner settings. - Use self-signed certificates: Configure certificates that verify TLS peers when connecting to the GitLab server.
- Autoscale with Docker Machine: Execute jobs on machines created automatically by Docker Machine.
- Autoscale GitLab Runner on AWS EC2: Execute jobs on auto-scaled AWS EC2 instances.
- Autoscale GitLab CI on AWS Fargate: Use the AWS Fargate driver with the GitLab custom executor to run jobs in AWS ECS.
- Graphical Processing Units: Use GPUs to execute jobs.
- The init system: GitLab Runner installs its init service files based on your operating system.
- Supported shells: Execute builds on different systems by using shell script generators.
- Security considerations: Be aware of potential security implications when running your jobs with GitLab Runner.
- Runner monitoring: Monitor the behavior of your runners.
- Clean up Docker cache automatically: If you are running low on disk space, use a cron job to clean old containers and volumes.
- Configure GitLab Runner to run behind a proxy: Set up a Linux proxy and configure GitLab Runner. Useful for the Docker executor.
- Handling rate limited requests.
- Configure GitLab Runner Operator.