Using Docker containers and executing job over SSH.Limit the number of concurrent jobs per-token.Use multiple tokens with multiple servers (even per-project).GitLab Runner has the following features. You can view things like the number of currently-running jobs and howĪfter a runner is configured and available for your project, your You can use Prometheus to monitor your runners. You can specify settings like logging and cache. In this file you can edit settings for a specific runner, or for all runners. This is a file that is installed during the runner installation process. The runner by editing the config.toml file. When the job runs, it uses the runner with the ruby tag. Tags are the only way to filter the list of available runners for a job.įor example, if a runner has the ruby tag, you would add this code to When a CI/CD job runs, it knows which runner to use by looking at the assigned tags. When you register a runner, you can add tags to it. This is how the runner knows which projects it’s available for. The scope of a runner is defined during the registration. Project runners are for individual projects.Group runners are for all projects and subgroups in a group.Shared runners are for use by all projects.There are three types of runners, based on who you want to have access: Should have access to it, or if you want to limit it to a specific GitLab group or project.

Who has access to runners in the GitLab UIīefore you register a runner, you should determine if everyone in GitLab To run your jobs, it’s sometimes referred to as a “Docker-in-Docker” configuration. When you install GitLab Runner in a Docker container and choose the On a virtual machine and have it use another virtual machine as an executor. These are only a few of the possible configurations. You might install GitLab Runner on a Linux server and register a runner that uses

If you want your CI/CD job to run commands in a custom Docker container,.

Runner on a Windows server and then register a runner that uses the shell executor.

If you want your CI/CD job to run PowerShell commands, you might install GitLab.

When you register a runner, you must choose an executor.Īn executor determines the environment each job runs in. In a Kubernetes cluster, or in auto-scaled instances in the cloud. However, you can also have a runner process jobs in a container, Runners usually process jobs on the same machine where you installed GitLab Runner. GitLab instance and the machine where GitLab Runner is installed. When you register a runner, you are setting up communication between your Runners are the agents that run the CI/CD jobs that come from GitLab. Keep GitLab Runner updated to the latest version, as isĪfter you install the application, you register If you host your own runners but host your repositories on , You must use a Runner version that is appropriate for the GitLab version, or upgrade the GitLab application.

It prevents the GitLab Runner from communicating with GitLab versions lower than 14.8. GitLab Runner 15.0 introduced a change to the

Perforce helix server download