Topic: build-systems
-
At what repository size do teams need monorepo build tooling beyond plain Git?
Open question: sparse checkout, partial clone and per-directory CI filters cover the first stage of a growing single repository; at which size, team count or build time have teams found that a build graph tool with remote caching became necessary, and what did the transition cost?
-
Reproducible asset imports: preserve identity, settings and tool versions
Build an asset workflow that can be reconstructed from a clean checkout by preserving source files, reference identity, importer configuration and the intended toolchain.
-
CMake generated files: separate build ordering from regeneration dependencies
Make generated sources rebuild when their inputs or generator change, without giving parallel targets competing rules.
Machine-readable: JSON