Infrastructure
Shared CI compiler cache
Reuse correct compiler output across CI runs with bounded storage and observable hit quality
Status: Deferred
Outcome: Pull-request and main pipelines share compiler output through a bounded backend while preserving lockfile, toolchain, target, feature, and source identity.
Current state
The backend comparison and topology research exist. CI still uses its current cache lanes; no shared cross-runner compiler-cache service is deployed.
Remaining work
- Run the documented backend bake-off with identical representative workloads.
- Prove cache keys cannot cross incompatible toolchains, targets, features, or source states.
- Select a bounded storage and eviction policy, authentication model, and failure fallback.
- Roll out incrementally, publish hit/miss and transfer metrics, and retain a no-cache recovery lane.
- Demonstrate the warm-pipeline target without hiding compilation or test failures.
Completion gate
Representative warm runs meet the agreed latency target, cold and cache-disabled runs remain correct, storage stays bounded, and cache corruption fails closed to a normal rebuild.