When the configuration cache is enabled and Gradle is able to find a compatible cache entry for the current build, it will load the tasks from the cache and run them in isolation.
Now, it does this also when storing a cache entry. All tasks run in parallel by default, even those within the same project, subject to dependency constraints. Gradle has always run tasks in parallel when it reuses a configuration cache entry. Starting in Gradle 8.0, tasks run in parallel from the first build when using the configuration cache. Configuration cache now enables more fine-grained parallelism than using the parallel execution. Improved configuration cache for parallelism on the first run This is an incubating feature that can significantly improve build performance. The configuration cache improves build time by caching the result of the configuration phase and reusing this for subsequent builds. Init scripts specified on the command-line using -init-script are now applied to buildSrc, in addition to the main build and all included builds. You can run the tests for buildSrc in the same way as other projects, as described above. In particular, this means that the tests of buildSrc and its subprojects are not built and executed when they are not needed. When Gradle builds the output of buildSrc it only runs the tasks that produce that output.
Tests for buildSrc are no longer automatically run Gradle 8.0 introduces an interpreter for the declarative plugins or includeBuild(someDir) in this settings script to include other builds in buildSrc. Improved script compilation performance Gradle's Kotlin DSL provides an alternative syntax to the traditional Groovy DSL with an enhanced editing experience in supported IDEs, with superior content assistance, refactoring, documentation, and more. New features, performance and usability improvements
0 kommentar(er)
