Skip to content

fix(build): resolve dependencies through the runner mirror in Docker builds - #79

Merged
hbrombeer merged 1 commit into
mainfrom
ci/maven-mirror-docker
Oct 17, 2026
Merged

hbrombeer merged 1 commit into
mainfrom
ci/maven-mirror-docker

Conversation

@hbrombeer

Copy link
Copy Markdown
Member

Mounts the runners' Maven mirror init script into the Gradle RUN of the Dockerfile:

--mount=type=secret,id=gradle_init,target=/root/.gradle/init.d/grounds-maven-mirror.init.gradle.kts,required=false

groundsgg/.github#36 passes the script as the BuildKit secret gradle_init whenever the runner has the mirror, so the image build resolves Maven Central, the Gradle Plugin Portal and PaperMC through it instead of hitting upstream (and its 429s). Without the secret the mount is skipped and the build resolves from upstream as before.

…builds

Mount the runners' Maven mirror init script, which the shared Docker
workflow passes as the BuildKit secret gradle_init, into the Gradle RUN.
Image builds then resolve through the mirror instead of Maven Central,
which has been failing release builds with 429s. Without the secret the
mount is skipped and Gradle resolves from upstream as before.
@hbrombeer
hbrombeer merged commit 57b0355 into main Oct 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant