You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,22 +75,21 @@ When routing a job to a self-hosted runner, {% data variables.product.prodname_d
75
75
- If the runner doesn't pick up the assigned job within 60 seconds, the job is re-queued so that a new runner can accept it.
76
76
- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels, then the job will remain queued until a runner comes online.
77
77
- If the job remains queued for more than 24 hours, the job will fail.
78
-
{% else %}
78
+
{% elsif ghes = 3.3 %}
79
79
- {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level.
80
-
{% ifversion ghes > 3.2 %}
81
80
- If {% data variables.product.prodname_dotcom %} finds an online and idle runner at a certain level that matches the job's `runs-on` labels, the job is then assigned and sent to the runner.
82
81
- If the runner doesn't pick up the assigned job within 60 seconds, the job is queued at all levels and waits for a matching runner from any level to come online and pick up the job.
83
-
- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job.
82
+
- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job.
83
+
- If the job remains queued for more than 24 hours, the job will fail.
84
84
{% else %}
85
-
- If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners.
86
-
- If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners.
87
-
- If there are no matching runners at any level, the job will fail.
85
+
1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level.
86
+
2. The job is then sent to the first matching runner that is online and idle.
87
+
- If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners.
88
+
- If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners.
89
+
- If there are no matching runners at any level, the job will fail.
90
+
- If the job remains queued for more than 24 hours, the job will fail.
88
91
{% endif %}
89
92
- If the job remains queued for more than 24 hours, the job will fail.
90
-
- If {% data variables.product.prodname_dotcom %} finds an online and idle runner at a certain level that matches the job's `runs-on` labels, the job is then assigned and sent to the runner.
91
-
- If the runner doesn't pick up the assigned job within 60 seconds, the job is queued at all levels and waits for a matching runner from any level to come online and pick up the job.
92
-
- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job.
93
-
- If the job remains queued for more than 24 hours, the job will fail.
94
93
{% else %}
95
94
1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level.
96
95
2. The job is then sent to the first matching runner that is online and idle.
0 commit comments