Is there a way to somehow have groups of projects, and then select which one is active? We currently have a big build with 400 modules (multiple apps). Local dev machines are managing just fine, so I'd like keep is this way - and having ability to build everything in one command is a superpower which I obviously want to keep. But not every team needs such bird's eye view of the whole build, mostly they're working on their part of the codebase. And some voiced that it would be nice if they only saw their part & it's dependency modules, to scope down the complexity Obvioulsy I know I can "hack" it via commenting out the projects in

settings.gradle

But isn't there something more sophisticated? Other than flipping it on its head, having per app builds & then one composite one (which I would not prefer)

Actually separating in multiple composite builds would have been my recommendation. So if a team wants to work on app A, only A and all its dependencies open while you can still have an uber-composite build that includes all apps to have them all together. But yeah, you can of course also have that "group of projects" logic without manual commenting. You have a turing-complete language at hand, so use it. Have `if`s or whatever around the `include`s and somehow decide which to include and which not like checking some project property or checking the contents of some file or whatever other way attracts you.

Btw wouldnt composite build be slower than equivalent "pure" build?

Afair depends could bei either way.

ooo perfect