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 builds and 5 shared libraries groups builds). However our results so far are quite disappointing. Any configuration cache miss triggers a massively increased configuration phase ( from 2s to 22s in our tests ). the apparent reason is that configuration on demand 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 build pre-alpha 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) (using gradle 8.9 and kotlin dsl)