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, 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. The default value is runner.Ĭheck_interval Defines the interval length, in seconds, between new jobs check. 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. The maximum number is all defined runners. They apply to all runners.Ĭoncurrent Limits how many jobs can run concurrently. ~/.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. Deploy to multiple servers using GitLab CI/CD Advanced configuration.Configure the Metrics Runner Referee for GitLab Runner.Precedence of Docker authorization resolving.Example 2: Mount a host directory as a data volume.
0 kommentar(er)
