Observação: no momento, não há suporte para os executores hospedados no GitHub no GitHub Enterprise Server. Você pode ver mais informações sobre o suporte futuro planejado no GitHub public roadmap.
About GitHub Actions on GitHub Enterprise Server
This article explains how site administrators can configure GitHub Enterprise Server to use GitHub Actions.
O GitHub Actions está disponível no GitHub Enterprise Server 3.0 ou superior. Se você estiver usando uma versão anterior do GitHub Enterprise Server, precisará fazer upgrade para usar o GitHub Actions. Para obter mais informações sobre como fazer upgrade da sua instância do GitHub Enterprise Server, confira "Sobre os upgrades para novas versões".
Por padrão, GitHub Actions não está habilitado para GitHub Enterprise Server. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from GitHub Actions without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable GitHub Actions for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
Antes de começar, você deve fazer um plano de como apresentar GitHub Actions para a sua empresa. Para obter mais informações, confira "Apresentação do GitHub Actions � sua empresa".
Se você estiver migrando sua empresa para GitHub Actions de outro provedor, há considerações adicionais. Para obter mais informações, confira "Como migrar sua empresa para o GitHub Actions".
Review hardware requirements
The CPU and memory resources available to your GitHub Enterprise Server instance determine the number of jobs that can be run concurrently without performance loss. GitHub recomenda um mínimo de 8 vCPU e 64 GB de memória para executar GitHub Actions.
The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
| vCPUs | Memória | Simultaneidade máxima |
|---|---|---|
| 32 | 128 GB | 1.000 trabalhos |
| 64 | 256 GB | 1.300 trabalhos |
| 96 | 384 GB | 2.200 trabalhos |
Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
If you plan to enable 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 GitHub Enterprise Server, see "Monitoring your appliance."
For more information about minimum hardware requirements for your GitHub Enterprise Server instance, see the hardware considerations for your instance's platform.
Para obter mais informações sobre como ajustar os recursos de uma instância existente, confira "Como aumentar a capacidade de armazenamento" e "Como aumentar os recursos de CPU ou de memória".
External storage requirements
To enable GitHub Actions on GitHub Enterprise Server, you must have access to external blob storage.
GitHub Actions uses blob storage to store data 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.
Aviso: o MinIO anunciou a remoção de Gateways MinIO. A partir de 1º de junho de 2022, as correções de suporte e bug para a implementação atual do Gateway do MinIO NAS estarão disponíveis somente para clientes pagos por meio de seu contrato de suporte LTS. Se você quiser continuar usando gateways MinIO com GitHub Actions, recomendamos migrar para o suporte do MinIO LTS. Para saber mais, confira a remoção agendada do Gateway do MinIO para GCS, Azure, HDFS no repositório minio/minio.
Before you enable GitHub Actions, you can test your storage configuration from the administrative shell with the ghe-actions-precheck utility. For more information, see "Command-line utilities" and "Accessing the administrative shell (SSH)."
Networking considerations
Se GitHub Actions estiver habilitado para sua empresa, apenas os proxies HTTP são compatíveis. Não há suporte para proxies SOCKS5 e HTTPS. For more information about using a proxy with GitHub Enterprise Server, see "Configuring an outbound web proxy server."
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
Observação: no momento, não há suporte para os executores hospedados no GitHub no GitHub Enterprise Server. Você pode ver mais informações sobre o suporte futuro planejado no GitHub public roadmap.
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 in your enterprise."
Fortalecimento geral de segurança para GitHub Actions
Caso deseje saber mais sobre as práticas de segurança do GitHub Actions, confira "Proteção de segurança para o GitHub Actions".
Reserved names
When you enable GitHub Actions for your enterprise, two organizations are created: github and actions. If your enterprise already uses the github organization name, github-org (or github-github-org if github-org is also in use) will be used instead. If your enterprise already uses the actions organization name, github-actions (or github-actions-org if github-actions is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore.