![]() Embedded Prometheus metrics HTTP server.Easy installation as a service for GNU/Linux, macOS, and Windows.Easy to use setup with support for Docker, Docker-SSH, Parallels, or SSH running environments.Automatic configuration reload without restart.Allows customization of the job running environment.Works on GNU/Linux, macOS, and Windows (pretty much anywhere you can run Docker).Supports Bash, PowerShell Core, and Windows PowerShell.Is written in Go and distributed as single binary without any other requirements.Using Docker containers with autoscaling on different clouds and virtualization hypervisors.Using Docker containers and executing job over SSH.Limit the number of concurrent jobs per-token.Use multiple tokens with multiple servers (even per-project).GitLab Runner has the following features. Use a runner to run jobsĪfter a runner is configured and available for your project, your You can view things like the number of currently-running jobs and how You can use Prometheus to monitor your runners. You can specify settings like logging and cache. In this file you can edit settings for a specific runner, or for all runners. This is a file that is installed during the runner installation process. The runner by editing the config.toml file. When the job runs, it uses the runner with the ruby tag. Tags are the only way to filter the list of available runners for a job.įor example, if a runner has the ruby tag, you would add this code to ![]() When a CI/CD job runs, it knows which runner to use by looking at the assigned tags. When you register a runner, you can add tags to it. This is how the runner knows which projects it’s available for. The scope of a runner is defined during the registration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |