Mirror Maven Central and retry, so a corrupt transfer stops killing the build

FixSecurityService
Shipped
August 5, 2026 at 9:06 PM UTC
Author
Kamo
Commit
8162347

The session security-level fix failed to deploy because bcprov-jdk18on:1.72 arrived corrupted — 'Tag mismatch' is a TLS auth-tag failure mid-transfer, not a missing artifact. The shared-lib stage had no mirror and no retry, so a single bad download took the whole build down; DocsService lost a build to the same thing on hibernate-core an hour earlier. Same treatment DocsService and the MLOS services already have: Google's GCS-backed Central mirror (byte-identical, not rate-limited) plus a 5-attempt retry, with settings.xml re-copied in the second stage because COPY --from brings the warmed repository but not the settings.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing