Options are debug, info, warn, error, fatal, and panic. View how this setting works with the Docker Machine executor (for autoscaling). If you use this value, the runner process exits with a critical error. For example, a value of 10 means no more than 10 jobs can run concurrently. Each ] section can define its own limit, but this value sets a maximum for all of those values combined. Setting Description concurrent Limits how many jobs can run concurrently, across all registered runners. GitLab Runner updated to benefit from the latest improvements and enhancements. Over time, the validation process will be refined to provide more accurate, comprehensive, and useful feedback. It may not catch all possible problems and the absence ofĪny messages does not guarantee that the config.toml file is flawless. To identify potential issues with their runner configuration. The configuration validation is a best effort and is currently only for informational purposes. Validator provides only info level messages.

on other systems Configuration validationĬonfiguration validation is a process that checks the structure of the config.toml file. ~/.gitlab-runner/ on *nix systems when GitLab Runner is./etc/gitlab-runner/ on *nix systems when GitLab Runner isĮxecuted as root ( this is also the path for service configuration).GitLab Runner also reloads the configuration in response to the SIGHUP signal. GitLab Runner checks for configuration modifications every 3 seconds and reloads if necessary. If a runner was already registered, you don’t need to register it again. In the ] section and most parameters in the global section, except for listen_address. GitLab Runner does not require a restart when you change most options. To do this, you modify a file called config.toml, which uses the TOML format. You can change the behavior of GitLab Runner and of individual registered runners. Configure the Metrics Runner Referee for GitLab Runner Advanced configuration.Runner images that use an old version of Alpine Linux.Helper image configuration for Kubernetes on Arm.Enable IAM roles for Kubernetes ServiceAccount resources.Use KMS key encryption in S3 bucket for runner cache.Precedence of Docker authorization resolving.Example 2: Mount a host directory as a data volume.

Advanced images