Skip to main content

このバージョンの GitHub Enterprise はこの日付をもって終了となります: 2022-09-28. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、最新バージョンのGitHub Enterpriseにアップグレードしてください。 アップグレードに関する支援については、GitHub Enterprise supportに連絡してください。

Getting started with GitHub Actions for GitHub Enterprise Server

Learn about enabling and configuring GitHub Actions on GitHub Enterprise Server for the first time.

Site administrators can enable GitHub Actions and configure enterprise settings.

ノート: GitHubホストランナーは、現在GitHub Enterprise Serverでサポートされていません。 GitHubパブリックロードマップで、計画されている将来のサポートに関する詳しい情報を見ることができます。

About GitHub Actions on GitHub Enterprise Server

This article explains how site administrators can configure GitHub Enterprise Server to use GitHub Actions.

GitHub Actions is available in GitHub Enterprise Server 3.0 or higher. If you're using an earlier version of GitHub Enterprise Server, you'll have to upgrade to use GitHub Actions. For more information about upgrading your GitHub Enterprise Server instance, see "About upgrades to new releases."

GitHub Actions is not enabled for GitHub Enterprise Server by default. 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.

始める前に、EnterpriseへGitHub Actionsをどのように導入するかを計画する必要があります。 詳しい情報については「EnterpriseへのGitHub Actionsの導入」を参照してください。

Enterpriseを他のプロバイダからGitHub Actionsに移行しているなら、追加で考慮すべきことがあります。 詳しい情報については「EnterpriseのGitHub Actionsへの移行」を参照してください。

Review hardware requirements

The CPU and memory resources available to GitHub Enterprise Serverインスタンス 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:

32128 GB1000ジョブ
64256 GB1300ジョブ
96384 GB2200ジョブ

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 GitHub Enterprise Serverインスタンス, see the hardware considerations for your instance's platform.


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.

警告: MinIOはMinIO Gatewaysの終了を発表しました。 2022年6月1日から、現在のMinIO NAS Gateway実装のサポートとバグフィックスは、有料のお客様にLTSサポート契約を通じてのみ利用できます。 GitHub Actionsと合わせてMinIO Gatewaysを使い続けたい場合は、MinIO LTSサポートへの移行をおすすめします。 詳しい情報については、minio/minioリポジトリのScheduled removal of MinIO Gateway for GCS, Azure, HDFSを参照してください。

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

Enterpriseで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:

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

ノート: GitHubホストランナーは、現在GitHub Enterprise Serverでサポートされていません。 GitHubパブリックロードマップで、計画されている将来のサポートに関する詳しい情報を見ることができます。

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, or manually syncing actions from

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.