![]() Note: These are the only storage providers that GitHub supports and can provide assistance with. GitHub Actions supports these storage providers: Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time.Īll other GitHub Actions data, such as the workflow files in a repository's file structure, are stored on the data storage volume for your GitHub Enterprise Server instance. The amount of storage required depends on your usage of GitHub Actions. ![]() GitHub Actions uses external blob storage to store data generated by workflow runs, such as workflow logs, caches, and user-uploaded build artifacts. To enable GitHub Actions on GitHub Enterprise Server, you must have access to external blob storage. For more information, see " Configuring rate limits." External storage requirements Optionally, you can limit resource consumption on your GitHub Enterprise Server instance by configuring a rate limit for GitHub Actions. For more information about monitoring the capacity and performance of GitHub Enterprise Server, see " Monitoring your appliance."įor more information about minimum hardware requirements for your GitHub Enterprise Server instance, see the hardware considerations for your instance's platform.įor more information about adjusting resources for an existing instance, see " Increasing storage capacity" and " Increasing CPU or memory resources." 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. This change in CPU represents a small portion of the changes to performance targets in this version of GitHub Enterprise Server. Note: Beginning with GitHub Enterprise Server 3.5, GitHub's internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. You may experience different performance depending on the overall levels of activity on your instance. ![]() GitHub measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: vCPUs 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. GitHub recommends a minimum of 8 vCPU and 64 GB memory to run GitHub Actions. 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. For more information, see " Migrating your enterprise to GitHub Actions." Review hardware requirements If you're migrating your enterprise to GitHub Actions from another provider, there are additional considerations. For more information, see " Introducing GitHub Actions to your enterprise." Then, you'll enable GitHub Actions for your enterprise, manage access permissions, and add self-hosted runners to run workflows.īefore you get started, you should make a plan for how you'll introduce GitHub Actions to your enterprise. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts and caches generated by workflow runs. 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. GitHub Actions is not enabled for GitHub Enterprise Server by default. This article explains how site administrators can configure GitHub Enterprise Server to use GitHub Actions. About GitHub Actions on GitHub Enterprise Server You can see more information about planned future support on the GitHub public roadmap. Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server.
0 Comments
Leave a Reply. |