RFR: 8341861: GHA: Use only retention mechanism to remove bundles
Doug Simon
dnsimon at openjdk.org
Thu Oct 31 09:48:17 UTC 2024
There have been numerous problems in the past with the logic for removing bundles:
* [JDK-8340418](https://bugs.openjdk.org/browse/JDK-8340418)
* [JDK-8336928](https://bugs.openjdk.org/browse/JDK-8336928)
* [JDK-8338402](https://bugs.openjdk.org/browse/JDK-8338402)
These problems can be avoided by relying on the [built-in GHA mechanism for specifying a retention limit](https://docs.github.com/en/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) for these bundles. This PR deletes the code that eagerly removes the bundles prior to the retention limit.
An additional benefit to preserving the artifacts longer is that it increases the window for being able to download them for extra testing under different configurations than those tested by GHA (e.g. same test, different GC flags).
-------------
Commit messages:
- let GHA bundle artifacts be cleaned up by built-in GHA retention mechanism
Changes: https://git.openjdk.org/jdk/pull/21801/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=21801&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8341861
Stats: 45 lines in 1 file changed: 0 ins; 45 del; 0 mod
Patch: https://git.openjdk.org/jdk/pull/21801.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/21801/head:pull/21801
PR: https://git.openjdk.org/jdk/pull/21801
More information about the build-dev
mailing list