Remarque : Les exécuteurs hébergés sur GitHub ne sont pas pris en charge sur GitHub Enterprise Server. Vous pouvez voir plus d’informations sur le support futur planifié dans la 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.
GitHub Actions n’est pas activé pour GitHub Enterprise Server par défaut. 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 and caches generated by workflow runs. Then, you'll enable GitHub Actions for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
Avant de démarrer, vous devez prévoir la façon dont vous allez présenter GitHub Actions à votre entreprise. Pour plus d’informations, consultez « Introducing GitHub Actions to your enterprise ».
Si vous migrez votre entreprise vers GitHub Actions à partir d’un autre fournisseur, il existe des considérations supplémentaires à prendre en compte. Pour plus d’informations, consultez « Migrating your enterprise to GitHub Actions ».
Review hardware requirements
The CPU and memory resources available to votre instance GitHub Enterprise Server determine the number of runners that can be configured without performance loss. GitHub a besoin d’un minimum de 8 processeurs virtuels et de 64 Go de mémoire pour exécuter GitHub Actions.
The peak quantity of connected runners 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 performance targets for GitHub Enterprise Server on a range of CPU and memory configurations.
| vCPUs | Memory | Maximum Connected Runners |
|---|---|---|
| 8 | 64 GB | 740 runners |
| 32 | 160 GB | 2700 runners |
| 96 | 384 GB | 7000 runners |
| 128 | 512 GB | 7000 runners |
GitHub measured maximum connected runners 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.
Notes:
-
Beginning with GitHub Enterprise Server 3.6, GitHub documents connected runners as opposed to concurrent jobs. Connected runners represents the most runners you can connect and expect to utilize. It should also be noted that connecting more runners than you can expect to utilize can negatively impact performance.
-
Beginning with GitHub Enterprise Server 3.5, GitHub's internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of GitHub Enterprise Server.
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 "Surveillance de votre instance."
For more information about minimum hardware requirements for votre instance GitHub Enterprise Server, see the hardware considerations for your instance's platform.
Pour plus d’informations sur l’ajustement des ressources pour une instance existante, consultez « Augmentation de la capacité de stockage » et « Augmentation des ressources processeur ou mémoire ».
Optionally, you can limit resource consumption on votre instance GitHub Enterprise Server by configuring a rate limit for GitHub Actions. For more information, see "Configuring rate limits."
External storage requirements
To enable GitHub Actions on GitHub Enterprise Server, you must have access to external blob storage.
GitHub Actions utilise le stockage blob externe pour stocker les données générées par les exécutions de workflow. Les données stockées incluent les journaux de workflow, les caches, et les artefacts de build chargés par l’utilisateur. 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.
All other GitHub Actions data, such as the workflow files in a repository's file structure, are stored on the data storage volume for votre instance GitHub Enterprise Server.
GitHub Actions supports these storage providers:
- Azure Blob storage
- Amazon S3
- Google Cloud Storage
- S3-compatible MinIO cluster
Note: These are the only storage providers that GitHub supports and can provide assistance with.
Il existe d’autres produits de stockage compatibles avec l’API S3 que ceux validés par les partenaires GitHub comme fonctionnant avec GitHub Actions sur GitHub Enterprise Server. Pour plus d’informations, consultez le référentiel Partenaires de stockage GHES.
Pour les produits de stockage validés via le programme de partenariat technologique GitHub, le fournisseur de stockage est responsable du support et de la documentation pour l’utilisation du produit de stockage avec GitHub Actions.
Networking considerations
Si GitHub Actions est activé pour votre entreprise, seuls les proxys HTTP sont pris en charge. Les proxys SOCKS5 et HTTPS ne sont pas pris en charge. 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 Google Cloud Storage
- Enabling GitHub Actions with MinIO 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 policies for GitHub Actions in your enterprise."
Adding self-hosted runners
Remarque : Les exécuteurs hébergés sur GitHub ne sont pas pris en charge sur GitHub Enterprise Server. Vous pouvez voir plus d’informations sur le support futur planifié dans la 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 "Ajout d’exécuteurs auto-hébergés."
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."
Renforcement de la sécurité générale pour GitHub Actions
Pour en savoir plus sur les pratiques de sécurité pour GitHub Actions, consultez « Durcissement de la sécurité pour 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.