Does anyone know how configure-on-demand is expected to apply in a larger composite build ? The documentation of either feature doesn’t mention the other.
We are exploring switching a monolithic build with 800 projects to a composite build (about 70 app projects and 5 multi-projects of shared libraries).
However our results so far are quite disappointing. Any configuration cache miss triggers a massively increased configuration phase (from 2s to 45s in our tests). The apparent reason is that configuration avoidance seems to be completely lost, or to only apply to the main build and not to any of the included builds.
We tried the isolated project pre-alpha feature but without much luck (config time goes down a bit to 10s but still configures way too many projects with regards to the requested tasks).
Note: we’re using Gradle 8.9
I thank you in advance for your answers.