enricobuehlerandClaude Fable 5 fcdb4d147d feat(ci): sccache everywhere a Rust job runs — one warm compile cache for the whole fleet ...

Backend = the existing RustFS (storage.unom.io, S3, region home-central;
LAN-pinned to home-central's address by ci-core's unbound so cache traffic
never hairpins the router). Repo secrets SCCACHE_ACCESS_KEY_ID/SECRET carry a
keypair scoped to the unom-ci-sccache bucket; keys embed compiler hash +
target + flags, so the Ubuntu, Fedora, cross-arm64 and MSVC universes share
one bucket without ever colliding.

Wired: ci (rust, rust-arm64), deb (all three), rpm, bench,
linux-client-screenshots, windows, windows-msix, windows-host.
CARGO_INCREMENTAL=0 alongside (sccache and incremental are mutually
exclusive, and incremental artifacts are what bloated the persistent Windows
target dirs anyway). The binary is baked into the builder images; a per-job
ensure-step (same pattern as the GTK4 packages step) keeps jobs green while
the running :latest predates the bake, and ensure-windows-toolchain.ps1
self-provisions sccache.exe on the Windows runner. windows-drivers stays
unwrapped (wdk-build owns its build env), arch/android/apple are follow-ups.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-29 21:04:05 +02:00

..

fedora-rpm.Dockerfile

feat(ci): sccache everywhere a Rust job runs — one warm compile cache for the whole fleet

2026-07-29 21:04:05 +02:00

pf-host-cc

build(ci): cross-compile and publish an aarch64 Linux client

2026-07-25 14:32:45 +02:00

rust-ci-arm64cross.Dockerfile

feat(ci): builder images move to the LAN registry, content-keyed; fan-out scoped by paths

2026-07-29 21:04:05 +02:00

rust-ci-noble.Dockerfile

feat(ci): sccache everywhere a Rust job runs — one warm compile cache for the whole fleet

2026-07-29 21:04:05 +02:00

rust-ci.Dockerfile

feat(ci): sccache everywhere a Rust job runs — one warm compile cache for the whole fleet

2026-07-29 21:04:05 +02:00