GitHub has made a significant move to expand its support for ARM architecture with the introduction of Windows ARM64 hosted runners, now in public preview and free for use in public repositories. This new offering is designed to cater to the growing need for ARM-based workflows, empowering developers to build, test, and deploy Windows applications efficiently, natively on ARM64 hardware. This blog post will explore the implications of this new feature, how to use it, and its impact on the developer community.
Windows ARM64 hosted runners are here to make running workflows on ARM architecture easier and more accessible. This newly released feature comes equipped with a Windows 11 Desktop image, packed with the necessary tools for developers to hit the ground running. These ARM-powered hosted runners are designed to bring the power of the ARM architecture to Windows users, offering a more energy-efficient and cost-effective way to run workloads.
What This Means for Developers
The new ARM64 hosted runners enable developers to create and manage workflows on Windows 11 without relying on virtualization tools. ARM-native developers will be able to run their builds directly on ARM64 architecture, which offers enhanced efficiency. This move follows GitHub’s release of Linux ARM64 hosted runners earlier in January, marking a notable step toward supporting the open-source community’s growing demands for ARM support.
These runners feature four virtual CPUs, which can handle compute-intensive tasks, giving developers more power for their workflows. Moreover, developers using public repositories can now access these ARM64 hosted runners for free, with certain limitations based on their plan’s concurrency. However, it’s important to note that these runners are currently only available for public repositories—private repositories will not support the new ARM64 label, and any attempt to use it there will result in a failed workflow.
How to Use the ARM64 Hosted Runners
To leverage the ARM64 hosted runners, developers can simply add a label to their workflow in public repositories. This will trigger the use of the Windows 11 Desktop image for ARM64. However, due to the fact that the feature is still in public preview, users may encounter longer queue times during periods of high demand. Additionally, while these runners are free in public repositories, the number of concurrent runs allowed will depend on the developer’s plan.
In partnership with Arm, GitHub has also introduced an updated Windows 11 Desktop ARM64 image, which includes preinstalled development tools. Developers can use this image for both the free offering and larger runner sizes. These tools enable a smoother, faster setup for ARM-native development without the need for time-consuming configuration. To select this image, users will need to create a new runner and choose the Microsoft Windows 11 Desktop by Arm Limited image from the console.
Getting Started
Developers eager to get started with ARM64 runners can do so right away by adding the appropriate label to their workflow file. More details and documentation on setting up and using ARM64 runners can be found in GitHub’s official guides and the community discussion forums.
What Undercode Says:
The move to provide free access to Windows ARM64 hosted runners is a significant step forward for ARM-native development on GitHub. As ARM architecture continues to rise in prominence, especially with the increasing demand for energy-efficient computing, this new offering will make it easier for developers to leverage ARM64 in their workflows without incurring additional costs. By providing free access in public repositories, GitHub is not only making this technology more accessible but also contributing to the broader growth of ARM-based solutions within the developer community.
For ARM-native developers, this feature removes the need for complex virtualization setups. They can now directly run their builds on ARM64 hardware, which is both faster and more cost-effective. Additionally, the inclusion of preinstalled development tools in the Windows 11 Desktop image ensures that developers can start their projects with minimal setup. This is a major time-saver for developers who may otherwise have spent hours configuring their environment.
On a larger scale, this move could lead to a greater shift towards ARM-based development. Historically, ARM architecture has been seen as a niche option, but with the growing availability of powerful ARM64 machines and the rise of mobile-first devices, ARM has begun to gain momentum in mainstream computing. GitHub’s support for ARM64 in its hosted runners could play a key role in accelerating this transition.
Another significant takeaway is the collaboration between GitHub and Arm. By working together, they are able to provide a tailored solution that optimizes performance for developers working within the ARM ecosystem. This partnership strengthens the idea that ARM could soon be a dominant architecture for software development, particularly as more industries turn to ARM-based devices for their low power consumption and high efficiency.
In terms of usage, the free nature of these hosted runners is particularly attractive for open-source projects. Developers who contribute to public repositories will now have access to high-powered resources without incurring any costs. This is a win for the open-source community, which often faces resource constraints when it comes to computing power.
However, while the feature is promising, it is still in public preview, and there may be some growing pains. As mentioned, longer queue times during peak usage hours could be a challenge. Additionally, the restriction of this feature to public repositories might limit its utility for some teams and developers who work in private projects. Nonetheless, this preview phase is likely to serve as valuable feedback for GitHub and Arm as they fine-tune the product for broader adoption.
Fact Checker Results:
- The Windows ARM64 hosted runners are currently in public preview and free for use in public repositories only.
- Users must add specific labels to their workflows to use these ARM64 runners.
- Private repositories are not supported at this stage; any attempt to use the label in private repos will result in failure.
References:
Reported By: github.blog
Extra Source Hub:
https://www.digitaltrends.com
Wikipedia
Undercode AI
Image Source:
Pexels
Undercode AI DI v2
