Get list of runners ( runner-1, runner-2).Here is an example of the loop in this case: If you set check_interval = 10, and there are two runners ( runner-1 and runner-2),Ī request is made each 10 seconds. Things get interesting when the runners are tied to a different GitLab instance.
Iterates over all sections, schedules a request for each, and sleeps for the calculated amount To do this, it divides the value of check_interval by the number of ] sections. GitLab Runner tries to ensure that subsequent requests for each runner are done in the specified interval. GitLab RunnerĬontains a loop that constantly schedules a request to the GitLab instance it’s configured for. The interval between requests to GitLab are more frequent than you might expect. If more than one ] section exists in config.toml, shutdown_timeout Number of seconds until the forceful shutdown operation times out and exits the process. listen_address Defines an address ( :) the Prometheus metrics HTTP server should listen on. sentry_dsn Enables tracking of all system level errors to Sentry. If set to 0 or lower, the default value is used. check_interval Defines the interval length, in seconds, between the runner checking for new jobs. The default value is runner, which contains ANSI escape codes for coloring. This setting has lower priority than the format set by command-line argument -log-format. This setting has lower priority than the level set by the command-line arguments -debug, -l, or -log-level. 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.
0 kommentar(er)
