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 3.0 以降で使用できます。 以前のバージョンの GitHub Enterprise Server を使用している� �合は、GitHub Actions を使用するようにアップグレードする必要があります。 GitHub Enterprise Server インスタンスのアップグレードの詳細については、「新しいリリースへのアップグレードについて」を参照してく� さい。

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 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 をエンタープライズに導入する方法を計画する必要があります。 詳細については、「GitHub Actions をエンタープライズに導入する」を参照してく� さい。

Enterprise を別のプロバイダーから GitHub Actions に移行する� �合は、追� の考慮事� �があります。 詳細については、「Enterprise を 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 では、GitHub Actions を実行するために、少なくとも 8 つの vCPU と 64 GB のメモリを推奨しています。

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:

vCPU 数	メモリ	最大コンカレンシー
32	128 GB	1,000 ジョブ
64	256 GB	1,300 ジョブ
96	384 GB	2,200 ジョブ

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.

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

既存のインスタンスのリソースの調整の詳細については、「ストレージ容量の増� 」および「CPU またはメモリ リソースの増� 」を参照してく� さい。

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

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

エンタープライズ用に 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 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

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."

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.