![]() ![]() 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |