Repository navigation
ci: use the GitHub Actions cache on hosted runners only - #33
Merged
Merged
Conversation
From the self-hosted runners on hbr1 the Actions cache stalled at 0 bytes for minutes and then crawled at about 1 MB/s (setup-node's npm cache in grounds-portal, 2026-09-30). That is slower than resolving from scratch. Gate setup-java's gradle cache and setup-gradle's cache on runner.environment. Self-hosted jobs use the Gradle build cache node the runners advertise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gradle-ci.yml,gradle-publish.ymlanddocker-gradle-build-push.yml:setup-java'scache: gradleandsetup-gradle's cache now apply only whenrunner.environment == 'github-hosted'. On the hbr1 pools they are off.Why: the Actions cache is downloaded from Azure blob storage. From hbr1 it stalled at 0 bytes for minutes and then crawled at ~1 MB/s (grounds-portal
setup-node, 2026-09-30, 287 MB). Measured from the same pods: nodejs.org 24 MB/s, registry.npmjs.org 15 MB/s. The cache is slower than resolving from scratch. The layer cache had the same problem (#29/#31).Self-hosted Gradle jobs keep the remote build cache node (
GRADLE_BUILD_CACHE_URL).publish-openapi-snapshot.ymlruns on hosted runners and is unchanged.Test:
test_gradle_caches_are_used_on_hosted_runners_only(9/9 green).