cleanup

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Clarify messages produced when deleting old output directories

+review REVIEW-6521

    • -1
    • +2
    ./DefaultBuildOutputDeleterTest.groovy
  1. … 4 more files in changeset.
Make sure the deleter doesn't do anything else

+review REVIEW-6424

    • -0
    • +2
    ./DefaultBuildOutputDeleterTest.groovy
Add BuildOutputCleanup implementation

- Detect Gradle version changes by keeping a `built.bin` in the project cache dir

- Register a listener that triggers clean up at the end of the configuration phase

- The build output cleanup cache only invokes the deleter when the marker file is missing

- Provide a registry that plugins can contribute output files to

- In LifecycleBasePlugin (the base plugin), register the buildDir and clean task target files

- Use a build operation when cleaning stale output files

+review REVIEW-6424

    • -0
    • +96
    ./BuildOutputCleanupCacheTest.groovy
    • -0
    • +54
    ./DefaultBuildOutputCleanupRegistryTest.groovy
    • -0
    • +92
    ./DefaultBuildOutputDeleterTest.groovy
  1. … 16 more files in changeset.