Repository navigation
ci(docker): use the GHA layer cache on GitHub-hosted runners only - #29
Merged
Merged
Conversation
From the self-hosted ARC runners the GHA cache downloads at tens of KB/s: the plugin-match 0.9.0 image spent 20+ minutes pulling one 93 MB cached layer at ~60 KB/s for a build that takes a few minutes uncached. Gate cache-from and cache-to on runner.environment so ARC builds run without a layer cache, and hosted runners keep it.
This was referenced Sep 29, 2026
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.
cache-from/cache-toofdocker-gradle-build-push.ymlnow apply only whenrunner.environment == 'github-hosted'; on ARC/self-hosted runners the build runs without a layer cache.Why: from the hbr1 ARC runners the GHA cache downloads at tens of KB/s. The
plugin-match:0.9.0tag build (2026-09-29) spent 20+ minutes on a single 93 MB cache layer (~60 KB/s, log:#15 sha256:67bf… 72.35MB / 92.76MB 1214.1s), and the base image was local immediately. The 60-minute ARC timeout in the same file exists for the same symptom.Tests:
tests/test_docker_workflow.pyknows therunnercontext andformat()and checks: public/hosted → gha cache-from and cache-to (mode=max); private/ARC → no cache-from, no cache-to. 4/4 green locally.Next step (separate): a layer cache of our own on hbr1 (persistent BuildKit daemon or a registry cache in the ARC cluster), so ARC builds get fast and cached.