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

Gradle Community

I just set up forwarding tasks in the included builds, e.g.
```// build.gradle.kts
tasks.register("foo") {
    dependsOn(gradle.includedBuilds.map { it.task(":foo") })
}```
```// included/build.gradle.kts
tasks.register("foo") {
    dependsOn(subprojects.map { "${it.path}:foo" })
}```

thanks, that partially works. Do you have an idea if not all subprojects have `task :foo`?

well that's up to how you set up your subprojects, but at that point it has nothing to do with included builds

maybe

```tasks.register("foo") {
    dependsOn(
        subprojects.map { subproject -&gt;
            subproject.tasks.matching { it.name == "foo" }
        }
    )
}```

Besides that using `tasks.matching` like that completely disables task-configuration avoidance, you should not reach into the subprojects model like that. That's why ephemient did it with the string-y dependency.

and combined with <https://stackoverflow.com/a/69179714/>, seems to be working well

```// modules/build.gradle.kts

// workaround for running <https://github.com/gradle/gradle/issues/22335>
tasks.addRule("Pattern: subprojectTasks_
<TASK>") {
    val taskName = this
    val taskPrefix = "subprojectTasks_"

    if (startsWith(taskPrefix)) {
        task(taskName) {
            val buildTaskName = taskName.removePrefix(taskPrefix).replaceFirstChar(Char::lowercase)
            val subprojectTasks = subprojects.map { subproject ->
                subproject.tasks.matching { it.name == buildTaskName }
            }
            dependsOn(subprojectTasks)
        }
    }
}```
which is basically the same functionality as <https://github.com/gradle/gradle/issues/22335> :+1:

This has exactly the same problems I just explained, so don't do this or you majorly hurt your builds