jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-06 06:02:35 -05:00
Code Issues Projects Releases Wiki Activity

Update using-high-performance-github-hosted-runners.md

Browse Source
This commit is contained in:
Martin Lopes
2022-07-28 14:21:12 +10:00
parent 7794b44b49
commit b8593f16d7
1 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
content/actions/using-github-hosted-runners/using-high-performance-github-hosted-runners.md
View File

@@ -17,7 +17,7 @@ When you add a {% data variables.product.prodname_dotcom %}-hosted runner to an
High performance {% data variables.product.prodname_dotcom %}-hosted runners are managed at the organization level, where they are arranged into groups that host multiple instances of the runner. Once you've created a group, you can then add a runner to the group and update your workflows to target the group. You can also control which repositories are permitted to send jobs to the group for processing. For more information about groups, see "[Managing access to GitHub-hosted runners using groups](/actions/using-github-hosted-runners/managing-access-to-github-hosted-runners-using-groups)."
In the following diagram, a class of hosted runner called `runner-16-core-ubuntu` has been defined with customized hardware and operating system configuration. Instances of this runner are then created and added to a group called `16-core-ubuntu-rg`. The group has been labelled `16-core-ubuntu`, and jobs use that label in their `runs-on` key to target the group for processing.
In the following diagram, a class of hosted runner named `16-core-ubuntu-runner` has been defined with customized hardware and operating system configuration. Instances of this runner are then created and added to a group called `16-core-ubuntu-rg`. The group has been assigned the label `16-core-ubuntu`, and jobs use that label in their `runs-on` key to target the group for processing.
![Diagram](/assets/images/hosted-runner.png)
@@ -88,7 +88,21 @@ jobs:
## Managing access to your runners
To ensure your developers have access to your runners, you will need to make sure that their organization has access (from the enterprise level) and that their repository has access from an organization level. For example, if you create an enterprise-level runner group and allocate it to an organization, you will still need to go into the organization level and specify repository level access
### Changing what organizations or repositories can access a runner group
{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
- For runner groups in an enterprise, under **Organization access**, modify what organizations can access the runner group.
- For runner groups in an organization, under **Repository access**, modify what repositories can access the runner group.
{% warning %}
**Warning**:
{% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}