![]() 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. These commands support the following arguments: Parameter Default Description -config See the configuration file section Specify a custom configuration file to be used gitlab-runner register 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) run SIGHUP Force to reload configuration file.įor example, to force a reload of a runner’s configuration file, run: Exit as soon as currently running builds do finish ( graceful shutdown). run, exec, run-single SIGQUIT Stop accepting a new builds. Use twice to exit now ( forceful shutdown). run, exec, run-single SIGINT, SIGTERM Abort all running builds and exit as soon as possible. Theįollowing commands support the following signals: Command Signal Action register SIGINT Cancel runner registration and delete if it was already registered. 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. You can check the list of commands by executing: GitLab Runner contains a set of commands you use to register, manage, and gitlab-runner stop doesn’t shut down gracefully GitLab Runner commands./usr/lib/gitlab-runner: No such file or directory.Access Denied when running the service-related commands. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |