참고: GitHub 호스트 실행기는 현재 GitHub Enterprise Server에서 지원되지 않습니다. 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는 기본적으로 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 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.
시작하기 전에 엔터프라이즈에 GitHub Actions를 도입하는 방법에 대한 계획을 세워야 합니다. 자세한 내용은 "Introducing GitHub Actions to your enterprise"을(를) 참조하세요.
엔터프라이즈를 다른 공급자의 GitHub Actions로 마이그레이션하는 경우 추가로 고려할 사항이 있습니다. 자세한 내용은 "Migrating your enterprise to GitHub Actions"을(를) 참조하세요.
Review hardware requirements
The CPU and memory resources available to GitHub Enterprise Server 인스턴스 determine the number of runners that can be configured without performance loss. GitHub은 GitHub Actions를 실행하기 위해 최소 8개의 vCPU 및 64GB 메모리가 필요합니다.
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 "인스턴스 모니터링."
For more information about minimum hardware requirements for GitHub Enterprise Server 인스턴스, see the hardware considerations for your instance's platform.
기존 인스턴스의 리소스 조정에 대한 자세한 내용은 "스토리지 용량 늘리기" 및 "CPU 또는 메모리 리소스 늘리기"를 참조하세요.
Optionally, you can limit resource consumption on 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는 외부 blob 스토리지를 사용하여 워크플로 실행으로 생성된 데이터터를 저장합니다. 저장된 데이터에는 워크플로 로그, 캐시, 및 사용자가 업로드한 빌드 아티팩트가 포함됩니다. 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 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.
GitHub 파트너가 GitHub Enterprise Server에서 GitHub Actions으로 작업하는 것으로 자체 유효성을 검사한 다른 S3 API 호환 스토리지 제품이 있습니다. 자세한 내용은 GHES Storage Partners 리포지토리를 참조하세요.
GitHub 기술 파트너 관계 프로그램을 통해 유효성을 검사한 스토리지 제품의 경우, 스토리지 공급자는 GitHub Actions에서 스토리지 제품을 사용하기 위한 지원 및 설명서를 담당합니다.
Networking considerations
엔터프라이즈에 GitHub Actions을 사용하도록 설정하면 HTTP 프록시만 지원됩니다. SOCKS5 및 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 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
참고: GitHub 호스트 실행기는 현재 GitHub Enterprise Server에서 지원되지 않습니다. 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 "자체 호스트형 실행기 추가."
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."
GitHub Actions에 대한 일반적인 보안 강화
GitHub Actions에 대한 보안 사례에 대해 자세히 알아보려면 "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.