NovFora Dev

Thread [GENERAL] What is your preferred CI/CD approach for monorepos?

Taylor Davis

Taylor Davis

4 months ago

Monorepo tooling has evolved tremendously with tools like Turbo, Nx, and Bazel addressing build isolation problems at scale. For teams managing 50+ services in a single repository, I've found that remote caching combined with graph-based change detection reduces pipeline times from ~18 minutes to under 2 minutes by only rebuilding affected downstream targets. However, this introduces significant tooling overhead — you need dedicated infrastructure for the cache and build system expertise within the team. For smaller organizations where monorepo size doesn't yet justify Bazel or Nx, a simpler approach with selective CI via git diff against your service directory structure works fine until complexity exceeds ~15 packages. What's been your breaking point — did you migrate to a dedicated build system due to slow pipelines, or do you prefer keeping the tooling minimal and accepting slower builds?

Join the conversation to leave a reply.

Sign in to reply

Related topics