Note: GitHub Actions support on Servidor de GitHub Enterprise 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "Enabling GitHub Actions and configuring storage."
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.
Note: GitHub Actions was available for Servidor de GitHub Enterprise 2.22 as a limited beta. 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."
The CPU and memory resources available to tu instancia de servidor de GitHub Enterprise determine the maximum job throughput for GitHub Actions.
Internal testing at GitHub demonstrated the following maximum throughput for Servidor de GitHub Enterprise instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance.
|vCPUs||Memory||Maximum job throughput|
|4||32 GB||Demo or light testing|
|8||64 GB||25 jobs|
|16||160 GB||35 jobs|
|32||256 GB||100 jobs|
If you enabled the beta of GitHub Actions for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of Servidor de GitHub Enterprise, see "Monitoring your appliance."
For more information about minimum hardware requirements for tu instancia de servidor de GitHub Enterprise, see the hardware considerations for your instance's platform.
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.
GitHub Actions requires the following permissions for the access key that will access the bucket:
GitHub Actions support on Servidor de GitHub Enterprise 2.22 was available as a limited beta. To configure GitHub Actions for your instance, upgrade to Servidor de GitHub Enterprise 3.0 or later. For more information, see the Servidor de GitHub Enterprise 3.0 release notes and "Upgrading Servidor de GitHub Enterprise."
- "Hardware considerations" for your platform in "Setting up a Servidor de GitHub Enterprise instance"
If GitHub Actions is enabled for your enterprise, only HTTP proxies are supported. SOCK5 and HTTPS proxies and Polipo are not supported. For more information about using a proxy with Servidor de GitHub Enterprise, see "Configuring an outbound web proxy server."
When you enable GitHub Actions for your enterprise, two organizations are created:
actions. If your enterprise already uses the
github organization name,
github-org is also in use) will be used instead. If your enterprise already uses the
actions organization name,
github-actions is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore.