About GitHub Actions for enterprises
GitHub Actions は、ビルド、テスト、デプロイのパイプラインを自動化できる継続的インテグレーションと継続的デリバリー (CI/CD) のプラットフォームです。 With GitHub Actions, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information, see エンタープライズの GitHub Actions について.
Before you introduce GitHub Actions to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use GitHub Actions to best support your unique needs.
Governance and compliance
You should create a plan to govern your enterprise's use of GitHub Actions and meet your compliance obligations.
Determine which actions and reusable workflows your developers will be allowed to use. First, decide whether you'll allow third-party actions and reusable workflows that were not created by GitHub. You can configure the actions and reusable workflows that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by GitHub. If you do allow third-party actions and reusable workflows, you can limit allowed actions to those created by verified creators or a list of specific actions and reusable workflows.
For more information, see リポジトリの GitHub Actions の設定を管理する, Organization について GitHub Actions を無効化または制限する, and エンタープライズで GitHub Actions のポリシーを適用する.
Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see 再利用可能なワークフローでの OpenID Connect の使用.
You can access information about activity related to GitHub Actions in the audit logs for your enterprise. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of GitHub. For more information, see Enterprise の監査ログ アクティビティのエクスポート and Enterprise の監査ログのストリーミング.
You can practice the principle of least privilege by administering custom organization roles for access to settings in your GitHub Actions CI/CD pipeline. For more information about custom organization roles, see カスタム組織の役割の情報.
Security
You should plan your approach to security hardening for GitHub Actions.
Security hardening individual workflows and repositories
Make a plan to enforce good security practices for people using GitHub Actions features within your enterprise. For more information about these practices, see GitHub Actions のセキュリティ強化.
You can also encourage reuse of workflows that have already been evaluated for security. For more information, see Innersourcing.
Securing access to secrets and deployment resources
You should plan where you'll store your secrets. We recommend storing secrets in GitHub, but you might choose to store secrets in a cloud provider.
In GitHub, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see GitHub Actions でのシークレットの使用.
You should consider adding manual approval protection for sensitive environments, so that workflows must be approved before getting access to the environments' secrets. For more information, see デプロイに環境の使用.
Security considerations for third-party actions
There is significant risk in sourcing actions from third-party repositories on GitHub. If you do allow any third-party actions, you should create internal guidelines that encourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see GitHub Actions のセキュリティ強化.
Private networking with GitHub-hosted runners
Azure VNET での GitHub ホストランナーを使用できます。 これにより、ランナーのネットワーク ポリシーを完全に制御しながら、CI/CD の GitHub マネージド インフラストラクチャを利用することができます。 Azure VNET の詳細については、Azure ドキュメントの「Azure Virtual Network とは」を参照してください。 For more information, see 企業内の GitHub ホストランナー向けの Azure プライベート ネットワークについて.
Innersourcing
Think about how your enterprise can use features of GitHub Actions to innersource automation. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see An introduction to innersource in GitHub Resources.
アクションを公開せずにエンタープライズ全体でアクションを共有するには、内部リポジトリにアクションを格納し、同じ組織またはエンタープライズ内の任意の組織が所有する他のリポジトリ内の GitHub Actions ワークフローへのアクセスを許可するようにリポジトリを構成します。 詳しくは、「アクションとワークフローを企業と共有する」をご覧ください。
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see ワークフローの再利用.
To provide a starting place for developers building new workflows, you can use workflow templates. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see 組織のワークフロー テンプレートを作成する.
Managing resources
You should plan for how you'll manage the resources required to use GitHub Actions.
Runners
GitHub Actions workflows require runners. You can choose to use GitHub-hosted runners or self-hosted runners. GitHub manages maintenance and upgrades for GitHub-hosted runners. For more information, see GitHub ホステッド ランナーの使用.
To manage your own resources, configuration, or geographic location of your runner machines, use self hosted runners. For more information, see 自己ホスト ランナーの概要.
If you want more control over the networking policies for your runners, use self-hosted runners or private networking options for GitHub-hosted runners. For more information about private networking options, see GitHub ホスト ランナーを使用したプライベート ネットワークについて.
If you are using self-hosted runners, you have to decide whether you want to use physical machines, virtual machines, or containers. Physical machines will retain remnants of previous jobs, and so will virtual machines unless you use a fresh image for each job or clean up the machines after each job run. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container.
You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see 自己ホストランナーの追加 and グループを使用してセルフホストランナーへのアクセスを管理する. You can also use policies to prevent people using repository-level self-hosted runners. For more information, see エンタープライズで GitHub Actions のポリシーを適用する.
You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see セルフホステッド ランナーによる自動スケーリング.
Finally, you should consider security hardening for self-hosted runners. For more information, see GitHub Actions のセキュリティ強化.
Storage
成果物を使うと、ワークフロー内のジョブ間でデータを共有し、ワークフローが完了したときに、そのワークフローのデータを保存できるようになります。 For more information, see ワークフローからのデータの格納と共有.
GitHub Actions also has a caching system that you can use to cache dependencies to speed up workflow runs. For more information, see 依存関係をキャッシュしてワークフローのスピードを上げる.
You can use policy settings for GitHub Actions to customize the storage of workflow artifacts, caches, and log retention. For more information, see エンタープライズで GitHub Actions のポリシーを適用する.
Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see GitHub Actions の課金について.
Tracking usage
You should consider making a plan to track your enterprise's usage of GitHub Actions, such as how often workflows are running, how many of those runs are passing and failing, and which repositories are using which workflows.
You can see basic details of storage and data transfer usage of GitHub Actions for each organization in your enterprise via your billing settings. For more information, see GitHub Actions の使用状況の表示.
For more detailed usage data, you can use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see webhook について.
Make a plan for how your enterprise can pass the information from these webhooks into a data archiving system. You can consider using "CEDAR.GitHub.Collector", an open source tool that collects and processes webhook data from GitHub. For more information, see the Microsoft/CEDAR.GitHub.Collector repository.
You should also plan how you'll enable your teams to get the data they need from your archiving system.