This message was deleted.

multiple tasks within the same project do not run in parallel, except for work submitted to Gradle workers which allows for some isolation, or configuration cache is enabled which prevents mutation of the project so parallelism of general tasks is safe

Ah! I didn’t know that. So in order to be parallelizable tasks needs to explicitly use the gradle workers?

either that or you need to explicitly enable configuration caching in your build (assuming your build is compatible), yes

Yes, I have parallelization enabled, and mostly every other task are currently executed in parallel (see above screenshot). Except the minification (which I do not own, is an Android task owned by Google) So it’s not a project configuration issue, is something in that task

Out of curiosity, how are you running

app:minifyBeta

and

app:minifyRelease

in a same

assemble

or

bundle

task?

I am requesting both separately to gradle at the same time with

./gradlew assembleBeta assembleRelease

, then minify for each build type is executed as part of them. Mostly all the the other tasks for both Beta and Release that are required to execute these two tasks are executed perfectly in parallel, except when it reaches to the minify, when it runs sequentially, one after the other