We've added a section in our docs on Gradle best p...

# gradle

[tapchicoma]

We've added a section in our docs on Gradle best practices (from our perspective): https://kotlinlang.org/docs/gradle-best-practices.html

[Vampire]

Nice.
Two comments:

If nothing changes in a build file (or its dependencies) the build file isn't recompiled.

That's a major understatement.
And also not related to configuration cache.
If nothing changed, the build file is not recompiled even without CC.
But everything up to executing the first task plus all normal dependency resolution is skipped with CC. No dependency downloading, no init script execution, no settings script execution, no build script execution, ...

This is the remote cache section

Like the local build cache, the remote build cache helps you save time by reusing outputs from other builds. It can retrieve task outputs from any earlier build you've already run, not just the last one.

sounds like the local build cache could only reuse results from last build run. But you are for sure aware that this is not the case. The point is, that you can reuse also build results from others, typically from CI machines. :-)

[IgnacioCarrion]

For me the link with text "Using Gradle with Continuous Integration systems" resolves to a 404 page: https://community.gradle.org/cookbook/ci/

[tapchicoma]

Fixed to https://cookbook.gradle.org/ci/

[tapchicoma]

@Vampire we've updated this page based on your feedback