This message was deleted.

The tasks are in the same project, right?

--parallel

is only affects multiple subprojects https://docs.gradle.org/current/userguide/performance.html#parallel_execution

Most projects consist of more than one subproject. Usually, some of those subprojects are independent of one another; that is, they do not share state. Yet by default, Gradle only runs one task at a time. To execute tasks belonging to different subprojects in parallel, use the

parallel

flag

Ahh gotcha -- ok, that makes sense then, yes they're part of the same project. Do you know if Gradle does support parallel task execution for tasks within the same project? 🤔

https://docs.gradle.org/current/userguide/performance.html#enable_configuration_cache

The configuration cache enables additional benefits as well. When enabled, Gradle:

• Executes all tasks in parallel, even those in the same subproject.

if you really wanted to get into the guts of Gradle, then it is possible to write tasks that do work in parallel. https://docs.gradle.org/current/userguide/worker_api.html But this is pretty specialised

Ahh that's great to know ☝️ I'm sure it'll be useful @ephemient enabling the configuration cache seemed to do it 🎉! https://scans.gradle.com/s/kucg6jxuau6xi/timeline