ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。

Enabling GitHub Actions and configuring storage

External storage must be configured as part of enabling GitHub Actions on GitHub Enterprise Server.

Site administrators can enable GitHub Actions and configure enterprise settings.

ここには以下の内容があります:

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

OR, learn how to contribute.

Note: GitHub Actions support on GitHub Enterprise Server 2.22 is a limited public beta. Review the external storage requirements below and sign up for the beta.

GitHubは、macOSランナーのホストにMacStadiumを使用しています。

About 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 artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. 必要なストレージ容量は、GitHub Actions の使用状況によって異なります。

GitHub Actions supports these storage providers:

  • Amazon S3
  • Azure Blob storage
  • S3-compatible MinIO Gateway for NAS

Amazon S3 permissions

If you use Amazon S3, GitHub Actions requires the following permissions for your AWS access key ID and secret:

  • s3:PutObject
  • s3:GetObject
  • s3:ListBucketMultipartUploads
  • s3:ListMultipartUploadParts
  • s3:AbortMultipartUpload
  • s3:DeleteObject

Enabling GitHub Actions

GitHub Actions support on GitHub Enterprise Server 2.22 is a limited public beta. Sign up for the beta.

参考リンク

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

OR, learn how to contribute.