slachiewicz opened a new pull request, #1859: URL: https://github.com/apache/maven-mvnd/pull/1859
Each POM change saves a new Mimir cache generation, and builds restore only the exact key or the newest fallback, so older generations just take up the 10 GB cache budget. A new `prune-caches` job runs after a push to `master` or a `.x` branch and keeps the newest key per family (`mimir2-<os>-<build>`) on that branch. It is the only job with `actions: write`, which deleting caches requires, and it checks out no code. If a save failed, the previous generation is still the newest and stays. Verified: the job's script with the delete replaced by `echo`, against the current caches → keeps one entry in each of the four families and deletes 9 older ones on `master`, 5 on `mvnd-1.x`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
