Optionally, to build and scale self-hosted runners automatically, use Actions Runner Controller (ARC).Optionally, further restrict the repositories that can use the runner.Create a group to manage access to the runners available to your enterprise.Deploy a self-hosted runner for your enterprise.Configure a limited policy to restrict the actions and reusable workflows that can run within your enterprise.In the guide, you'll complete the following tasks. This guide shows you how to apply a centralized management approach to self-hosted runners for GitHub Actions in your enterprise. For more information, see ' Using GitHub-hosted runners.' GitHub-hosted runners are outside the scope of this guide. For more information, see ' About self-hosted runners.'Īlternatively, you can use runner machines that GitHub hosts. All runners can run Linux, Windows, or macOS. Your runner machine connects to GitHub Enterprise Cloud using the GitHub Actions self-hosted runner application. Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud. You can host your own runner machine to execute jobs, and this machine is called a self-hosted runner. With GitHub Actions, developers can write and combine individual tasks called actions to create custom workflows.

For more information, see ' About GitHub Actions for enterprises.' GitHub Actions allows members of your enterprise to improve productivity by automating every phase of the software development workflow. About self-hosted runners for GitHub Actions

Download the new version ArcRunner