Repository navigation
Debug enabled gradle.properties file is not cleaned up in post #549
Description
When running actions in debug mode a gradle.properties file is created in ~/.gradle/. However, the post step does not appear to remove this file.
When using a self-hosted runner, where jobs are not run in containers, subsequent jobs may end up inadvertently running gradle with INFO level output producing much more logging than desired.
Reacted by José Carlos Cieni Júnior, Mike Cumings, Sutaek Oh and 남동민
Activity
diskerr commentedon Jun 12, 2025
We're also running into this issue on our self-hosted runners with a persistent volume. Once that
gradle.propertiessticks around, every subsequent build on that runner gets forced into noisyINFOlevel logs. I hope this gets fixed soon.fix(setup-gradle): restore temporary debug gradle.properties after job (
Merge pull request #27 from rafaelmeloreisnovo/contrib/upstream-549-d…