Note: GitHub-hosted runners are not currently supported on Servidor de GitHub Enterprise. You can see more information about planned future support on the Itinerario público de GitHub.
This article explains how site administrators can configure Servidor de GitHub Enterprise to use GitHub Actions. It covers the hardware and software requirements, presents the storage options, and describes the security management policies.
Review hardware considerations
Note: If you're upgrading an existing Servidor de GitHub Enterprise instance to 3.0 or later and want to configure GitHub Actions, note that the minimum hardware requirements have increased. For more information, see "Upgrading Servidor de GitHub Enterprise."
If you configure GitHub Actions for the users of your Servidor de GitHub Enterprise instance, you may need to provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. For more information about monitoring the capacity and performance of Servidor de GitHub Enterprise, see "Monitoring your appliance."
For more information about resource requirements for Servidor de GitHub Enterprise, see the hardware considerations for your instance's platform.
For more information about adjusting resources for an existing instance, see "Increasing storage capacity" and "Increasing CPU or memory resources."
External storage requirements
To enable GitHub Actions on Servidor de GitHub Enterprise, you must have access to external blob storage.
GitHub Actions uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of GitHub Actions. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time.
GitHub Actions supports these storage providers:
- Azure Blob storage
- Amazon S3
- S3-compatible MinIO Gateway for NAS
Note: These are the only storage providers that GitHub supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. Contact us to request support for additional storage providers.
Enabling GitHub Actions with your storage provider
Follow one of the procedures below to enable GitHub Actions with your chosen storage provider:
- Enabling GitHub Actions with Azure Blob storage
- Enabling GitHub Actions with Amazon S3 storage
- Enabling GitHub Actions with MinIO Gateway for NAS storage
Managing access permissions for GitHub Actions in your enterprise
You can use policies to manage access to GitHub Actions. For more information, see "Enforcing GitHub Actions policies for your enterprise."
Adding self-hosted runners
Note: GitHub-hosted runners are not currently supported on Servidor de GitHub Enterprise. You can see more information about planned future support on the Itinerario público de GitHub.
To run GitHub Actions workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "Adding self-hosted runners."
Managing which actions can be used in your enterprise
You can control which actions your users are allowed to use in your enterprise. This includes setting up GitHub Connect for automatic access to actions from GitHub.com, or manually syncing actions from GitHub.com.
For more information, see "About using actions on Servidor de GitHub Enterprise."
General security hardening for GitHub Actions
If you want to learn more about security practices for GitHub Actions, see "Security hardening for GitHub Actions."