Configuration cache passes locally but breaks in CI pipeline
Goal Decide whether the production pipeline should enable Gradle's configuration cache, which serializes the task graph at configuration time for faster builds. Constraints Local runs often use a warm Gradle daemon and a populated ~/.gradle directory, while CI agents start cold with a clean GRADLE_USER_HOME . Plugins may perform unsupported work at execution
gradle
cypressio