Incremental Build vs Full Rebuild for Large-Scale Site Consistency

Build Strategy for High-Volume Content

Managing a Jekyll site with thousands of pages creates a significant trade-off between development velocity and output reliability. When utilizing jekyll build --incremental, the build time is reduced by regenerating only changed files, which is critical for maintaining a fast local feedback loop.

However, the incremental feature is documented as experimental. There is a known risk that global site state, complex collections, or specific plugin hooks may not trigger correctly, potentially leaving stale assets or incorrect URLs in the _site directory that a full jekyll build would otherwise resolve.

For a production CI/CD pipeline where consistency is mandatory but build durations are constrained, the choice between these two modes remains unclear.

• Does the incremental build reliably track dependencies for all standard collection types in Jekyll 4.x?
• What is the recommended strategy to ensure output parity between incremental local builds and full production builds?