GitLab Runner is the open source project that is used to run your jobs and send the results back to GitLab. It is used in conjunction with GitLab CI, the open-source continuous integration service included with GitLab that coordinates the jobs.
GitLab Runner is written in Go and can be run as a single binary, no language specific requirements are needed.
It is designed to run on the GNU/Linux, macOS, and Windows operating systems. Other operating systems will probably work as long as you can compile a Go binary on them.
If you want to use Docker make sure that you have version
v1.5.0 at least
- Allows to run:
- multiple jobs concurrently
- use multiple tokens with multiple server (even per-project)
- limit number of concurrent jobs per-token
- Jobs can be run:
- using Docker containers
- using Docker containers and executing job over SSH
- using Docker containers with autoscaling on different clouds and virtualization hypervisors
- connecting to remote SSH server
- Is written in Go and distributed as single binary without any other requirements
- Supports Bash, Windows Batch and Windows PowerShell
- Works on GNU/Linux, OS X and Windows (pretty much anywhere you can run Docker)
- Allows to customize the job running environment
- Automatic configuration reload without restart
- Easy to use setup with support for Docker, Docker-SSH, Parallels or SSH running environments
- Enables caching of Docker containers
- Easy installation as a service for GNU/Linux, OSX and Windows
- Embedded Prometheus metrics HTTP server
In the following table you can see the compatibility chart between GitLab and GitLab Runner.
|GitLab Runner / GitLab||9.0.x (03.2017)||9.1.x (04.2017)||9.2.x (05.2017)||9.3.x (06.2017)||9.4.x (07.2017)||9.5.x (08.2017)||10.0.x (09.2017)|
GitLab Runner can be installed and used on GNU/Linux, macOS, FreeBSD and Windows. You can install it using Docker, download the binary manually or use the repository for rpm/deb packages that GitLab offers. Below you can find information on the different installation methods:
- Install using GitLab's repository for Debian/Ubuntu/CentOS/RedHat (preferred)
- Install on GNU/Linux manually (advanced)
- Install on macOS (preferred)
- Install on Windows (preferred)
- Install as a Docker Service
- Install in Auto-scaling mode using Docker machine
- Install on FreeBSD
- Install on Kubernetes
- Install the nightly binary manually (development)
Once GitLab Runner is installed, you need to register it with GitLab.
Learn how to register a GitLab Runner.
GitLab Runner implements a number of executors that can be used to run your builds in different scenarios. If you are not sure what to select, read the I am not sure section. Visit the compatibility chart to find out what features each executor supports and what not.
To jump into the specific documentation of each executor, visit:
- Docker Machine and Docker Machine SSH (auto-scaling)
- 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.
- Auto-scaling using Docker machine Execute jobs on machines that are created on demand using Docker machine.
- 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 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.
Read the FAQ for troubleshooting common issues.
The description of release process of the GitLab Runner project can be found in the release documentation.
Contributions are welcome, see
CONTRIBUTING.md for more details.
See the development documentation to hack on GitLab Runner.
Visit Changelog to view recent changes.
This code is distributed under the MIT license, see the LICENSE file.
Last updated 2017-10-09