Allow organization or repository variable to dictate the Actions runner - #81087
Conversation
This updates the performance and E2E GitHub Actions workflows to be directed by an organization or repository variable to use a specific runner or configured group of runners, while still defaulting to the default. When a maintainer sets `RUNNER_GROUP` to a runner label, the configured jobs will run on that runner instead without editing the workflow. This is useful for directing longer-running jobs to a dedicated runner during high-load contribution periods, such as Contributor Days or deadlines within a release window. See also https://core.trac.wordpress.org/ticket/65749.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
lancewillett
changed the title
There was a problem hiding this comment.
Code is fine. No blockers.
Naming nit: Since this variable contains the runner label such as release-runner could you name it RUNNER_LABEL instead? RUNNER_GROUP could be confused with GitHub’s separate runner-group setting.
Good point! I went with |
…er (#81087) * Allow variable to dictate the Actions runner. This updates the performance and E2E GitHub Actions workflows to be directed by an organization or repository variable to use a specific runner or configured group of runners, while still defaulting to the default. When a maintainer sets `RUNNER_GROUP` to a runner label, the configured jobs will run on that runner instead without editing the workflow. This is useful for directing longer-running jobs to a dedicated runner during high-load contribution periods, such as Contributor Days or deadlines within a release window. See also https://core.trac.wordpress.org/ticket/65749. * Rename variable. * Change to `RUNNERS_NAME` to avoid confusion. Co-authored-by: desrosj <desrosj@git.wordpress.org> Co-authored-by: lancewillett <lancewillett@git.wordpress.org>
3 participants
What?
This updates the performance and E2E GitHub Actions workflows to be directed by an organization or repository variable to use a specific runner or configured group of runners, while still defaulting to the default.
When a maintainer sets
RUNNER_GROUPto a runner label, the configured jobs will run on that runner instead without editing the workflow.See also Core-65749.
Why?
This is useful for directing longer-running jobs to a dedicated runner during high-load contribution periods, such as Contributor Days or deadlines within a release window.
Use of AI Tools
None.