A platform team is designing a CI pipeline for a monorepo containing 20 independent microservices. The current pipeline builds and tests all services on every commit, resulting in 40-minute build times for even single-service changes. Which optimization strategy best addresses this?

Question

Accepted Answer

B. Implement path-based pipeline triggering that only builds and tests services affected by changed files. Path-based triggering only rebuilds and retests services with changed files or changed dependencies, dramatically reducing CI cycle time in a monorepo. This is the standard CI optimization for large monorepos. Option c reduces elapsed time but still runs unnecessary work for every unaffected service. Option d introduces human error and undermines the correctness guarantees that automated CI provides.

A platform team is designing a CI pipeline for a monorepo containing 20 independent microservices. The current pipeline builds and tests all services on every commit, resulting in 40-minute build times for even single-service changes. Which optimization strategy best addresses this?

Related Questions

Discussion