This message was deleted.

Gradle per-se is happy to run multiple times at the same time usually. Maybe that is some limitation of bug in the Kotlin Gradle plugin and you should report it to JetBrains

yeah seems like it. This is an odd usecase though so I think I will just workaround given that repro is just a race condition. Prob just do another TF module that will run the assemble on all modules so that the parallel gradle invocations of the others will be up to date. Then if I set a depends on in TF their graph will deal with the ordering.

Are all the gradle invocations using the same gradle daemon?

I suspect no on the assumption gradle does some sort of file lock to ensure only one daemon gets used at a time. I'll do a --stop before my next apply and see how it actually behaves.