You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting gradle-home-cache-cleanup: true, the action will attempt to remove all unused files from Gradle User Home before saving the state.
When running a build with state loaded from the configuration-cache, many files in Gradle User Home (eg dependency jars) are not necessarily recorded as being used during the build.
Taken together, this means that after a successful build with configuration-cache reuse, the saved Gradle User Home will have no dependencies. This can result in a ClassNotFoundException failure in subsequent builds.
The text was updated successfully, but these errors were encountered:
bigdaz
changed the title
Cache cleanup incompatible with configuration-cache reuse
Cache cleanup is incompatible with configuration-cache reuse
Feb 9, 2024
bigdaz
changed the title
Cache cleanup is incompatible with configuration-cache reuse
Cache cleanup should not run after configuration-cache reuse
Jul 17, 2024
When a build runs with config-cache reuse, many necessary files are not marked
as being used during the build execution. This means that subsequent cache-cleanup
may remove files that are required for subsequent builds.
This change disables cache-cleanup whenever a build runs with config-cache reuse.
Fixes#19
When setting
gradle-home-cache-cleanup: true
, the action will attempt to remove all unused files from Gradle User Home before saving the state.When running a build with state loaded from the configuration-cache, many files in Gradle User Home (eg dependency jars) are not necessarily recorded as being used during the build.
Taken together, this means that after a successful build with configuration-cache reuse, the saved Gradle User Home will have no dependencies. This can result in a
ClassNotFoundException
failure in subsequent builds.The text was updated successfully, but these errors were encountered: