- Ya
- 9 Agosti 2026, 02:17 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 82ff1d3
Every Docker stage starts from a cold ~/.m2 and refetches the whole dependency tree, so Central sees the full weight of every concurrent service build. It answers with 429s and, twice today, corrupt transfers: BillingService died on "Tag mismatch" fetching tomcat-embed-core. SecurityService and mlos-doc-orchestration-service already mirror through Google GCS, which serves byte-identical artifacts and is not rate-limited; the rest of the fleet did not. settings.xml goes into every Maven stage — the COPY --from that warms ~/.m2/repository does not carry it, so a later stage would go straight back to Central.