Getting started with GitHub Actions for GitHub Enterprise Server

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」を参照してください。

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 と 64 GB のメモリが必要です。

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.

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.

• AWS
• Azure
• Google Cloud Platform
• Hyper-V
• OpenStack KVM
• VMware

既存インスタンスのリソース調整の詳細については、「ストレージ容量の増加」と「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

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

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.