What is 'GitHub Enterprise Server Actions' caching and what storage does it use?
Select an answer to reveal the explanation.
Short Explanation and Infographic
When you run Actions on GHES, the cache (npm packages, Maven artifacts, etc.) lives on blob storage on the GHES instance itself. Unlike GitHub.com where cache is managed for you, on GHES you're responsible for provisioning enough storage and setting the cache size limit.
Full explanation below image
Full Explanation
GitHub Actions caching on GitHub Enterprise Server uses dedicated blob storage on the GHES instance. Key details: (1) Cache storage is separate from repository storage — it uses a blob storage volume. (2) Administrators set the maximum Actions cache size in Management Console settings. (3) Cache is scoped per repository (not per runner). (4) When the cache limit is reached, older cache entries are evicted automatically. (5) Storage planning: Actions cache can consume significant disk space, especially for large dependency sets. Self-hosted runners on GHES can also access the Actions cache service. Planning for Actions on GHES requires additional storage beyond repository needs, particularly if many repositories use dependency caching in their workflows.