This message was deleted.
# community-support
s
This message was deleted.
j
Hi Basil. Tasks in the same project can only run in parallel when the Configuration Cache is enabled. Then Gradle will run tasks in parallel as the task graph allows. Otherwise it is not supported. There is a catch right now, that it only works on the “2nd run” (when the configuration is taken from cache). But this is planned to be improved for the Stable Configuration Cache. For more details see https://github.com/gradle/gradle/issues/14624 If you start a new project with Gradle now, I would recommend to enable the Configuration Cache right away. It’s soon gonna be stable and if you start using it from the beginning, you won’t use any of the “wrong patterns” that break it.
b
Hello Jendrik, Thank you for the information. I will try this at my end.
👍 1
j
One correction, that I just remembered: If you use the Worker API in a task action, other tasks are allowed to start in parallel while work is performed inside the worker thread/process. This is independent of the
org.gradle.parallel=true
and
org.gradle.unsafe.configuration-cache=true
setting
👍 2