From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Something like this might work:
```gradle.includedBuilds.forEach { includedBuild -&gt;
  project.tasks.named("clean") {
    dependsOn(includedBuild.task(":clean"))
  }
}```


Bear in mind that this can only target a specific task (note the leading colon).

Not sure what that would do to a `build-logic` included build either!

hrm, lemme see. I was going down that road, but didn't see what I needed, but I think I was thinking backwards.

I was trying to make the root projects' clean task depend on the included build's clean task

Solution:

Root project build.gradle.kts:
```val includedBuildCleanTasks = gradle.includedBuilds.map {includedBuild -&gt;
    includedBuild.task(":clean")
}

tasks.register("clean") {
    dependsOn(includedBuildCleanTasks)
}```
Included builds' root project build.gradle.kts:
```tasks.register("clean") {
    val subprojectCleanTasks = project.subprojects.map { sp -&gt;
        sp.tasks.findByName("clean")
    }
    dependsOn(subprojectCleanTasks)
    description = "Deletes build directories of all plugins"
}```


Didn't think you could make a task depend on either a `TaskReference` or `TaskContainer`