The exit code is zero when the service is running and non-zero when the service is not running. This command prints the status of the GitLab Runner service. This command stops and then starts the GitLab Runner service. This command stops the GitLab Runner service. This command starts the GitLab Runner service.
This command stops and uninstalls GitLab Runner from being run as an Specify the password for the user that executes the builds Specify the user that executes the builds Specify the root directory where all data is stored when builds are run with the shell executor Specify if the service should integrate with system logging service When run on Windows or as super-user, it accepts the -user flag whichĪllows you to drop privileges of builds run with the shell executor. It accepts different sets ofĪrguments depending on which system it’s run on. This command installs GitLab Runner as a service. Specify a custom configuration file to use Use them to install, uninstall, start, and stop the runner service.Īll service related commands accept these arguments: Parameter The following commands allow you to manage the runner as a system or user Gitlab-runners reset-token -all-runners Service-related commands There are two options to register a runner: Gitlab-runner register adds a new configuration entry. You can use multiple configurations in a single installation of GitLab Runner. This command registers your runner in GitLab by using the GitLab Runners API. Specify a custom configuration file to be used These commands support the following arguments: Parameter Use the following commands to register a new runner, or list and verify log-level value, -l value Log level (options: debug, info, warn, error, fatal, panic) īelow we explain what each command does in detail. log-format value Choose log format (options: runner, text, json) cpuprofile value write cpu profile to file
Help, h Shows a list of commands or help for one command Read-logs reads job logs from a file, used by kubernetes executor (internal) Health-check check health for a specific address Gitlab-runner command Īrtifacts-downloader download and extract build artifacts (internal)Īrtifacts-uploader create and upload build artifacts (internal)Ĭache-archiver create and upload cache artifacts (internal)Ĭache-extractor download and extract cache artifacts (internal)Ĭache-init changed permissions for cache paths (internal) Exit as soon as currently running builds do finish ( graceful shutdown).įor example, to force a reload of a runner’s configuration file, run: Use twice to exit now ( forceful shutdown).
Theįollowing commands support the following signals: CommandĬancel runner registration and delete if it was already registered.Ībort all running builds and exit as soon as possible. You can use system signals to interact with GitLab Runner. To specify a custom configuration file, use the -c or -config flag, or use So you can have a multiple different configurations on a single machine. Most of the commands accept an argument to specify a custom configuration file, GitLab Runner configuration uses the TOML format.Įxecuted as super-user ( root): /etc/gitlab-runner/config.tomlĮxecuted as non-root: ~/.gitlab-runner/config.toml In the case of Windows, you may need to run the command prompt as INFO Starting multi-runner from /etc/gitlab-runner/config.toml. Saving system ID state file: access denied.gitlab-runner stop doesn’t shut down gracefully./usr/lib/gitlab-runner: No such file or directory.Access Denied when running the service-related commands.