|
| 1 | +--- |
| 2 | +title: Introduction to GitHub Arm-hosted Runners |
| 3 | + |
| 4 | +weight: 2 |
| 5 | + |
| 6 | +### FIXED, DO NOT MODIFY |
| 7 | +layout: learningpathall |
| 8 | +--- |
| 9 | +GitHub Arm-hosted runners for Windows are now available in public preview, providing a powerful and efficient way to build, test and deploy your Windows applications on Arm without the need for virtualization. These runners come with a Windows 11 Desktop image, equipped with many tools to get started with your workflows. |
| 10 | + |
| 11 | +### What are GitHub Arm-hosted Runners? |
| 12 | + |
| 13 | +Runners are the machines that execute jobs in a GitHub Actions workflow. An Arm-hosted runner is managed by GitHub and uses the Arm architecture, meaning you don't need to provide a server to run Actions workflows. GitHub provides the system and runs the Action workflows for you. |
| 14 | + |
| 15 | +Arm-hosted runners are available for public repositories at no cost, subject to [standard usage limits](https://docs.github.com/en/actions/administering-github-actions/usage-limits-billing-and-administration#usage-limits). They are powered by Microsoft Azure Cobalt 100 processors, based on the Arm Neoverse N2, with 4 vCPUs and Armv9-A features, including Scalable Vector Extension 2 (SVE2). |
| 16 | + |
| 17 | +### How to Use GitHub Arm-hosted Windows Runners |
| 18 | + |
| 19 | +To leverage the GitHub Windows Arm64 hosted runners, you will need to use the following label in your public repository workflow runs: |
| 20 | + |
| 21 | +```yaml |
| 22 | +runs-on: windows-11-arm |
| 23 | +``` |
| 24 | +
|
| 25 | +Please note that this label will not work in private repositories, the workflow will fail if you add it. |
| 26 | +
|
| 27 | +Two types of GitHub-hosted runners are available; standard runners, and larger runners. Larger runners are differentiated from standard runners because users can control the amount of RAM, the number of CPUs, and configure the allocated disk space. You can also use the Windows 11 Desktop Arm Image with larger runners. To use this image on large runners, you will need to create a new runner. |
| 28 | +
|
| 29 | +### How can I create an GitHub Arm-hosted Windows large runner? |
| 30 | +
|
| 31 | +Arm-hosted runners are created at the organization level. |
| 32 | +
|
| 33 | +Navigate to your organization and select the `Settings` tab. On the left pane, select `Actions->Runners`. |
| 34 | + |
| 35 | +On the `Runners` page, select the `New runner` drop-down on the top right, and then select `New GitHub-hosted runner`. |
| 36 | + |
| 37 | + |
| 38 | + |
| 39 | + |
| 40 | +Specify a name for the runner, this is the `runs-on` field in your workflows so make the name clear for others who use it. |
| 41 | + |
| 42 | +Choose Windows ARM64 for the platform and click `Save`. |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | +Specify the operating system image for the runner, select `Microsoft Windows 11 Desktop by Arm Limited`, and click `Save`. |
| 47 | + |
| 48 | + |
| 49 | + |
| 50 | +Select the size of the large runner you need and and click `Save`. |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | +The `Capacity` section includes the maximum concurrency, which is the number of jobs to run at the same time. Specify at least two for this Learning Path. |
| 55 | + |
| 56 | +You can also set the runner group for this runner. The runner group controls the settings for this runner. Pay attention to the runner group as you may need to return to the runner group settings if any configuration changes are needed. |
| 57 | + |
| 58 | + |
| 59 | + |
| 60 | +Finally, click `Create runner`. |
| 61 | + |
| 62 | +Your new Arm-hosted runner Windows large runner is ready to use. You will need to remember the runner name for use in your workflows with the `runs-on` label. |
| 63 | + |
| 64 | +### Check the server hardware used by the Arm-hosted Windows Runners |
| 65 | +The Arm-hosted runners are powered by Microsoft Azure Cobalt 100 processors, based on the Arm Neoverse N2, with 4 vCPUs and Armv9-A features, including Scalable Vector Extension 2 (SVE2). |
| 66 | + |
| 67 | +The output from running the `wmic` command on the Arm-hosted runner is below. |
| 68 | + |
| 69 | + |
| 70 | + |
| 71 | + |
| 72 | +### Check Installed Software on the Arm-hosted Windows Runners |
| 73 | + |
| 74 | +To find out more about the software installed on the Arm-hosted runners, visit the [GitHub Actions Partner Images repository](https://github.com/actions/partner-runner-images/). Check the [image documentation](https://github.com/actions/partner-runner-images/blob/main/images/arm-windows-11-image.md) for a list of software packages installed on the Windows 11 by Arm Limited image. You can also use this repository to report issues or request additional software. |
| 75 | + |
0 commit comments