Every sandboxed build kept its own Gradle home under /root: on mih09 six
repositories held six dependency caches and six provisioned JDKs, about
5 GiB of a 16 GiB SSD. The Docker runner has had a persistent Gradle
volume since step 11; the werkdock runner never got the equivalent.
werkdock.gradleHome names a host directory that every sandbox naming the
same path mounts as /gradle-user-home, with GRADLE_USER_HOME pointing
there — the same pair the Docker runner uses. Beside /root rather than
over /root/.gradle, so a leftover per-repository cache is unused, not
hidden.
Pinned and opt-in: the path is mounted read-write, and a shared cache
is shared trust. Set once in the defaults block of ~/.werkator.yml.
Every sandboxed build kept its own Gradle home under /root: on mih09 six
repositories held six dependency caches and six provisioned JDKs, about
5 GiB of a 16 GiB SSD. The Docker runner has had a persistent Gradle
volume since step 11; the werkdock runner never got the equivalent.
werkdock.gradleHome names a host directory that every sandbox naming the
same path mounts as /gradle-user-home, with GRADLE_USER_HOME pointing
there — the same pair the Docker runner uses. Beside /root rather than
over /root/.gradle, so a leftover per-repository cache is unused, not
hidden.
Pinned and opt-in: the path is mounted read-write, and a shared cache
is shared trust. Set once in the defaults block of ~/.werkator.yml.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Every sandboxed build kept its own Gradle home under /root: on mih09 six
repositories held six dependency caches and six provisioned JDKs, about
5 GiB of a 16 GiB SSD. The Docker runner has had a persistent Gradle
volume since step 11; the werkdock runner never got the equivalent.
werkdock.gradleHome names a host directory that every sandbox naming the
same path mounts as /gradle-user-home, with GRADLE_USER_HOME pointing
there — the same pair the Docker runner uses. Beside /root rather than
over /root/.gradle, so a leftover per-repository cache is unused, not
hidden.
Pinned and opt-in: the path is mounted read-write, and a shared cache
is shared trust. Set once in the defaults block of ~/.werkator.yml.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
mi
merged commit 83f38c6ffa into main2026-09-17 15:08:14 +02:00
mi
deleted branch shared-gradle-home2026-09-17 15:08:14 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every sandboxed build kept its own Gradle home under /root: on mih09 six
repositories held six dependency caches and six provisioned JDKs, about
5 GiB of a 16 GiB SSD. The Docker runner has had a persistent Gradle
volume since step 11; the werkdock runner never got the equivalent.
werkdock.gradleHome names a host directory that every sandbox naming the
same path mounts as /gradle-user-home, with GRADLE_USER_HOME pointing
there — the same pair the Docker runner uses. Beside /root rather than
over /root/.gradle, so a leftover per-repository cache is unused, not
hidden.
Pinned and opt-in: the path is mounted read-write, and a shared cache
is shared trust. Set once in the defaults block of ~/.werkator.yml.
Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com