You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "slachiewicz (via GitHub)" <gi...@apache.org> on 2026/10/19 00:45:22 UTC

[PR] Prune superseded integration-test cache generations [maven]

slachiewicz opened a new pull request, #13616:
URL: https://github.com/apache/maven/pull/13616

   Each change to the integration-test POMs saves a new `it-m2-repo` generation per OS, and the IT job restores 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 and keeps the newest `it-m2-repo` key per OS on the 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 selection run against the current caches → keeps one entry per OS and deletes 8 older ones (2.2 GB) here and 15 (3.8 GB) on `maven-3.9.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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Prune superseded integration-test cache generations [maven]

Posted by "slachiewicz (via GitHub)" <gi...@apache.org>.
slachiewicz merged PR #13616:
URL: https://github.com/apache/maven/pull/13616


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org