lobipromotions.blogg.se

tls-ca-file When using HTTPS, file that contains the certificates to verify the peer. token The runner’s authentication token, which is obtained during runner registration. Setting Description name The runner’s description. The ] sectionĮach ] section defines one runner. If you are using the GitLab Runner Docker image, you must expose port 8093 byĪdding -p 8093:8093 to your docker run command.

When your runner instance is already running, you might need to execute gitlab-runner restart for the changes in the section to be take effect. It should be defined outside the ] section. The section should be specified at the root level, not per runner. The section lets users interact with jobs, for example, in the Repeated after all requests for the other runners and their sleep periods are called. If you define more runners, the sleep interval is smaller. Each one takes 5 seconds, so it’s approximately 10 seconds between subsequent requests for runner-1. GitLab instance, this GitLab instance also receives a new request from this runnerīetween the first request for runner-1 and second request for runner-1 If runner-1 and runner-2 are connected to the same

In this example, a request from the runner’s process is made every 5 seconds. Calculate the sleep interval ( 10s / 2 = 5s).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, 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 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. 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/ 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.Runner images that use an old version of Alpine Linux.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.