GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. With GitHub Actions, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of GitHub Actions, see "Understanding 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."
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.
You should create a plan to govern your enterprise's use of GitHub Actions and meet your compliance obligations.
Determine which actions your developers will be allowed to use. First, decide whether you'll enable access to actions from outside your instance. 如果企业中的用户需要访问来自 GitHub.com 或 GitHub Marketplace 的其他操作，有几个配置选项。 For more information, see "About using actions in your enterprise."
Then, decide whether you'll allow third-party actions that were not created by GitHub. You can configure the actions 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, you can limit allowed actions to those created by verified creators or a list of specific actions. For more information, see "Managing GitHub Actions settings for a repository", "Disabling or limiting GitHub Actions for your organization", and "Enforcing policies for GitHub Actions in your enterprise."
You can access information about activity related to GitHub Actions in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of GitHub. For more information, see "Searching the audit log."
You should plan your approach to security hardening for GitHub Actions.
Make a plan to enforce good security practices for people using GitHub Actions features within your enterprise. For more information about these practices, see "Security hardening for GitHub Actions."
You can also encourage reuse of workflows that have already been evaluated for security. For more information, see "Innersourcing."
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 "Encrypted secrets."
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 "Using third-party actions."
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.
To provide a starting place for developers building new workflows, you can use starter workflows. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "Creating starter workflows for your organization."
You should plan for how you'll manage the resources required to use GitHub Actions.
GitHub Actions workflows require runners. You will need to host your own runners by installing the GitHub Actions self-hosted runner application on your own machines. For more information, see "About self-hosted runners."
Decide whether you want to use physical machines, virtual machines, or containers for your self-hosted runners. 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 "Adding self-hosted runners" and "Managing access to self-hosted runners using groups."
Finally, you should consider security hardening for self-hosted runners. For more information, see "Security hardening for GitHub Actions."
构件允许您在工作流程完成后，分享工作流程中作业之间的数据并存储数据。 For more information, see "Storing workflow data as artifacts."
You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."
By default, GitHub Enterprise Server stores build logs and artifacts for 90 days, and this retention period can be customized. For more information, see "Usage limits, billing, and administration."
If you want to retain logs and artifacts longer than the upper limit you can configure in GitHub Enterprise Server, you'll have to plan how to export and store the data.
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 use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see "About webhooks."
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
You should also plan how you'll enable your teams to get the data they need from your archiving system.