-
Notifications
You must be signed in to change notification settings - Fork 7
Specifying Standby Runners
vzakaznikov edited this page Jan 24, 2024
·
2 revisions
You can define standby runner groups to always be ready to pick up your jobs using a custom configuration file.
✋ Note: | Standby runner groups can only be defined using a configuration file. See Using a Configuration File for more details. |
---|
Standby runners are always active and allow jobs to be picked up immediately.
More than one standby runner group can be specified in the standby_runners. Each group is defined using the standby_runner object that has labels, count, and replenish_immediately attributes.
schema: |
"standby_runners": {
"type": "array",
"items": {
"type": "object",
"properties": {
"labels": {
"type": "array",
"items": {
"type": "string"
}
},
"count": {
"type": "integer"
},
"replenish_immediately": {
"type": "boolean"
}
}
}
} |
---|
where,
- labels specifies an array of labels with which standby runners in this group should be created
- count specifies the count of how many runners should be created for the group
- replenish_immediately specifies if the sandby runners should be replenished as soon as they become busy after picking up a job; default: true
For example,
config.yaml: |
config:
standby_runners:
- labels:
- type-cx21
count: 2
replenish_immediately: true |
---|
Developed and maintained by the TestFlows team.
- Home
- Installation
- Quick Start
- Getting Started Tutorial
- Basic Configuration
- Specifying the Maximum Number of Runners
- Specifying the Maximum Number of Runners Used in Workflow a Run
- Recycling Powered‐Off Servers
- Skipping Jobs
- Using Custom Label Prefix
- Jobs That Require the Docker Engine
- Specifying The Runner Type
- Specifying The Runner Location
- Specifying The Runner Network
- Specifying The Runner Image
- Specifying The Custom Runner Server Setup Script
- Specifying The Custom Runner Server Startup Script
- Disabling Setup or Startup Scripts
- Specifying Standby Runners
- Using Caching Volumes
- Specifying Logger Configuration
- Listing All Current Servers
- Opening The SSH Client To The Server
- Deleting All Runners and Their Servers
- Using a Configuration File
- Using Project Configuration Files
- Specifying SSH Key
- Specifying Additional SSH Keys
- Running as a Service
- Running as a Cloud Service
- Scaling Up Runners
- Scaling Down Runners
- Handling Failing Conditions
- Meta Labels
- Estimating Costs
- Listing Images
- Deleting Images
- Creating Custom Images
- Embedded Monitoring Dashboard
- Prometheus Metrics
- Program Options