Mac终端gradle clean build耗时过长，咨询构建差异及提速方案

1. Build Scope & Task Execution #

• Terminal gradle clean build: Runs the full Gradle lifecycle. The clean task deletes all existing build outputs (classes, jars, test results, etc.), forcing a complete rebuild from scratch. The build task then executes all dependent tasks—including compileJava, test, check, assemble, and any custom project tasks—with no incremental optimizations.
• IntelliJ Build Project: Defaults to incremental builds, only compiling modified source files and skipping tasks that don’t need re-running (e.g., tests if no test code changed). It also uses its own IDE-specific cache and may skip non-essential Gradle tasks that aren’t required for running the project in the IDE.

2. Gradle Environment & Configuration #

• Terminal: Uses the project’s Gradle Wrapper (v8.2) with settings from gradle.properties (where cache-related config is disabled). It may lack daemon or parallel execution by default, leading to repeated startup overhead and slower task processing.
• IntelliJ: May use your local Gradle v8.4 instead of the wrapper, and automatically enables the Gradle daemon, parallel execution, and its own caching layer—even when Gradle’s built-in cache is turned off. The IDE also optimizes JVM settings for build performance behind the scenes.

3. Caching Mechanisms #

• Terminal: Relies solely on Gradle’s built-in build cache, which you’ve disabled due to past failures. Without caching, every task runs from scratch every time.
• IntelliJ: Uses an independent IDE-specific cache to reuse compiled classes and task outputs, drastically cutting build times even when Gradle’s cache is off.

1. Fix and Re-enable Gradle Build Cache #

Cache failures are almost always due to corruption, not the feature itself. Try these steps:

• Delete corrupted cache files: Run rm -rf ~/.gradle/caches in terminal.
• Uncomment cache lines in gradle.properties: Add org.gradle.caching=true to re-enable local build caching, which reuses task outputs across builds to avoid redundant work.

2. Enable Gradle Daemon #

The daemon keeps a Gradle process running in the background, eliminating startup overhead for subsequent builds. Add this to gradle.properties:

org.gradle.daemon=true

Verify it’s running with ./gradlew --status.

3. Enable Parallel Execution #

For multi-module projects, parallel execution runs tasks across modules simultaneously. Add to gradle.properties:

org.gradle.parallel=true

4. Skip Unnecessary clean Tasks #

Only run gradle clean build when you need a full reset (e.g., after major dependency changes). For regular development, use gradle build instead—it performs an incremental build, reusing existing outputs where possible.

5. Skip Non-Essential Tasks #

If you don’t need tests or lint checks every build, skip them with the -x flag:

gradle build -x test -x check

Note: Only do this if you’re confident skipped tasks won’t miss critical issues.

6. Align Gradle Versions #

Update your project’s Gradle Wrapper to match your local v8.4 (newer versions include performance improvements):

./gradlew wrapper --gradle-version 8.4

7. Optimize JVM Settings #

Give Gradle more memory and use a modern garbage collector. Add these lines to gradle.properties:

org.gradle.jvmargs=-Xmx4g -XX:+UseParallelGC -XX:MaxMetaspaceSize=1g

Adjust -Xmx based on your available RAM (e.g., -Xmx6g if you have 16GB+ RAM).

内容的提问来源于stack exchange，提问作者sleepy_soul