Hey guys, I'm curious about the configuration cache behaviour. These are the steps happen: 1. Configuration phase 2. Storing in CC 3. Loading from CC This happen when there is no CC or something changed. I just ask myself if its necessary to load the cache, after it has been stored... Its actually "not a big deal", but for me it just feels strange that it loads again. Everything should be already there/in memory, otherwise it couldn't have been saved, right? 😁 So out of curiosity, is this "needed" to behave like that? Or could this be improved?

Your project is configured with Android NDK 26.3.11579264, but the following plugin(s) depend on a different Android NDK version: - installed_apps requires Android NDK 27.0.12077973 Fix this issue by using the highest Android NDK version (they are backward compatible). Add the following to /Users/nadinjoma/StudioProjects/parental_control_app/android/app/build.gradle.kts: android { ndkVersion = "27.0.12077973" ... } lib/main.dart469: Error: No named parameter with the name 'excludeSystemApps'. excludeSystemApps: true, ^^^^^^^^^^^^^^^^^ ../../.pub-cache/hosted/pub.dev/installed_apps-1.6.0/lib/installed_apps.dart1632: Context: Found this candidate, but the arguments don't match. static Future<List<AppInfo>> getInstalledApps([ ^^^^^^^^^^^^^^^^ Target kernel_snapshot_program failed: Exception FAILURE: Build failed with an exception. * What went wrong: Execution failed for task 'appcompileFlutterBuildDebug'.

Process 'command '/Users/nadinjoma/development/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:

Run with --stacktrace option to get the stack trace.

Run with --info or --debug option to get more log output.

Run with --scan to get full insights.

Get more help at https://help.gradle.org.

BUILD FAILED in 1m 30s Running Gradle task 'assembleDebug'... 91.5s Error: Gradle task assembleDebug failed with exit code 1. any help??

Hi folks. My environment has dozens of JUnit 3 suite classes - we typically invoke one suite per CI runner - and these are invoked in a proprietary way i.e. not using Gradle. Now I'm registering dozens of

Test

tasks (one per suite) but am finding the need to have a custom "label" for each task . For example, labeling them one of [red, green, blue]. I was considering using

ext

to set a custom property, i.e.

task.ext.color = 'blue'

, or I could register a custom extension type. Are either of these approaches going to break configuration caching? Will querying the extension at build-time cause the task to be eagerly created? In pseudocode, I might have a CI trigger which runs something like:

tasks.withType(Test).collect {
  it.hasExtension(MyCustomColorExtension) and
  it.color == 'blue'
}...

This would enumerate the subset of tasks I need to pass to another downstream system.

I'm trying to enable the configuration cache on one of our project, but I get the following error within the Kotlin Compile task Is there anything I may try?

i am trying to run my flutter program and i have java 17 it shows this error can anyone help please

Launching lib\main.dart on Android SDK built for x86 in debug mode... Support for Android x86 targets will be removed in the next stable release after 3.27. See https://github.com/flutter/flutter/issues/157543 for details. FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring root project 'android'.

Could not resolve all files for configuration ':classpath'.

> Could not find com.android.tools.buildG 8.0.0. Searched in the following locations: - https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/ 8.0.0/gradle- 8.0.0.pom - https://repo.maven.apache.org/maven2/com/android/tools/build/gradle/ 8.0.0/gradle- 8.0.0.pom Required by: project : * Try:

Run with --stacktrace option to get the stack trace.

Run with --info or --debug option to get more log output.

Run with --scan to get full insights.

* Get more help at https://help.gradle.org BUILD FAILED in 6m 41s Error: Gradle task assembleDebug failed with exit code 1 Exited (1).

Hi all I'm trying to enable configuration cache for my project. I'm running

./gradlew assemble --configuration-cache

First run

Calculating task graph as no cached configuration is available for tasks: assemble
[Build log]
Configuration cache entry stored.

Second run

Calculating task graph as configuration cache cannot be reused because the file system entry 'build/classes/java/main' has been created.
[Build log]
Configuration cache entry stored.

Third run

Reusing configuration cache.
[Build log]
Configuration cache entry reused.

How can I debug what depends on

build/classes/java/main

? I'm using

plugins {
    id 'java'
    id "org.springframework.boot" version "3.4.5"
    id "io.spring.dependency-management" version "1.1.7"
    id "org.openapi.generator" version "7.13.0"
    id "org.sonarqube" version "6.1.0.5360"
    id 'jacoco'
    id "io.freefair.lombok" version "8.13.1"
}

and gradle 8.14.

Is there a configuration-cache compatible way of doing the following: Taking a list of configuration (ConfigurationContainer, NamedDomainObjectCollection) and turn them into an input to a task? For example calling

.map { it.incoming.resolutionResult.root }

causes us to realize/create each configuration? So even if the output of this is cc-compatible, it still causes us to realized the collection. Is this fine if it's done in a configureEach, as it'll only be realized if the task is actually called? It just seems like unlike Property/Provider, there's no map/flatMap for the named object collections.

<!channel> if you are interested in knowing more about Configuration Cache, what's coming up in Gradle 9 and beyond, and how to adopt Configuration cache in your builds and plugins... join us for the webinar with @Alex Semin tomorrow! https://gradle.com/events/gradle-configuration-cache-05-25/ We will also use this channel for Q&A, and you are welcome to start adding questions for Alex and the Configuration team below! We will answer everything either asynchronously or during the call

Do not hesitate to ask questions here, we will ask Alex. I am also capturing questions so that we can incorporate them in our docs

And a micro-survey for those who are watching or using Configuration Cache - https://app.sli.do/event/4dkRGVpaxiLiadtgrCj3za

A meeting ran long and I missed the first two third of the webinar. Will a recording be shared?

This message was deleted.

FYI CC issue in Gradle 9 and Kotlin Multiplatform https://kotlinlang.slack.com/archives/C19FD9681/p1748577543128899?thread_ts=1748362393.256609&amp;cid=C19FD9681

We’re looking at enabling Configuration Cache across our company (1000+ devs, 1000s of Gradle based repos, 100s of plugins). It’s quite a mammoth task at this scale, so we want to try and do this incrementally - ie enable it for one workflow like compilation, then work up to running tests, then all the other tasks. This avoids us spending years rewriting all our plugins before we get any value. Has anyone worked out a way to incrementally enable Configuration Cache? Our original plan was: 1. Get our plugins in shape so that compilation (

classes testClasses

etc) fully works 2. Enable CC using gradle properties _in warn mode_ on repos so that CC will work for compilation, just not save the cache state for everything other set of tasks 3. In each repo, specify the max number of allowed CC problems to be the current number of problems. Use this max number of problems as a ratchet to stop people adding new problems (ie stop the bleeding). 4. Automatically reduce this max allowed number of CC problems down as we fix issues 5. CC just works on workflows where everything is fixed 6. Eventually we work down to 0 issues on the whole

./gradlew build

and we hard enforce configuration cache on that repo However, this doesn’t work, as

warn

mode doesn’t do what we expect.

warn

mode is apparently only supposed to be used for diagnosing initial problems. If you use

warn

mode, the build will still go wrong or error on configuration cache issues:

We don’t recommend using

problems=warn

for anything but initial configuration cache adoption attempts to see more issues at once.

From the Gradle team here

With

problems=warn

, it is expected that your build might run incorrectly if there are problems detected.

From here This has kind of stopped us in our tracks, as we can’t just always run in warn mode for all our repos and keep track of the problems. Is there any way to gradually enable configuration cache? Our options seem to be: • Hard enforce CC on each repo using the gradle property. However, this requires getting to completely fixed in each repo in all the plugins and workflows it uses. This will take us a very long time due to the scale of our Gradle plugins (built over the last 13 years - many are quite crusty). • Have our devs opt-in to CC by manually using

--configuration-cache

. This feels like a non-starter to me. Devs shouldn’t have to worry about this and won’t necessarily know which tasks are CC supported or not. It doesn’t enable it in IntelliJ without another IntelliJ Plugin. We can’t stop CC problems from regressing. Is there some other approach?

I'm encountering ``cannot be reused because an input to unknown location has changed` and I wanted to debug it. How can I compare the inputs of the two configuration cache entries? Looks like someone was able to do it here: https://github.com/gradle/gradle/issues/25469#issuecomment-2614299897

It is sad

org.gradle.api.tasks.diagnostics.internal.ConfigurationDetails

is not publicly-available. Any third-party task like

dependencies

would effectively duplicate

ConfigurationDetails

to support the configuration cache. Is there a possibility to make

ConfigurationDetails

public? I would assume it could be a feature-reduced variation of

Configuration

.

Can I somehow fetch

ResolvedArtifact

(coordinates + file) from a

Configuration

so it is compatible with configuration cache? I see I can pass

incoming.resolutionResult.rootComponent

(which is

Provider<ResolvedComponentResult>

) as a task property, however, I do not see how could I fetch artifact file location from the

ResolvedComponentResult

Is there a way to download “pom files” for the set of “groupartifactversion” in a task action or work action? Currently I have something as follows while neither

project

nor

project.dependencies

is compatible with CC:

val artifactResolutionResult = project.dependencies.createArtifactResolutionQuery()
    .forComponents(requests.map { it.first })
    .withArtifacts(MavenModule::class, MavenPomArtifact::class)
    .execute()

val results = artifactResolutionResult.resolvedComponents
    .associate { it.id to it.getArtifacts(MavenPomArtifact::class) }

I run into a behavior when using configuration cache in combination with artifact transforms I'm not sure how to wrap my head around for our test setup we want to do something like that:

FileCollection mainRuntime = mainSourceSet.getRuntimeClasspath();
FileCollection testRuntime = testSourceSet.getRuntimeClasspath();
FileCollection testOnlyFiles = testRuntime.minus(mainRuntime);
test.doFirst(task -> test.environment("es.entitlement.testOnlyPath", testOnlyFiles.getAsPath()));

ideally I would want to replace the requirement for using

test.doFirst

by replacing it with

test.environment("es.entitlement.testOnlyPath", getProviderFactory().provider(() -> testOnlyFiles.getAsPath()));

Now in theory that works okay but it breaks as soon as we enable configuration cache and have artifact transforms in declared that are registered against configurations that include internal dependencies complaining about the expected jar to transform not yet available (well it did not build yet). My understanding is that with having those configurations declared as

@InputFiles

gradle understands its buildable and does handle it as expected. Given that

environment

is

@Input

we circumvent the buildable part I assume. In this case would you just keep the doFirst block as is or do you have another idea how to solve that properly?

Folks, help my poor vacation brain. When is an input property not prematurely evaluated and serialized to the CC entry? I thought with

abstract class MyTask : DefaultTask() {
    @get:Input
    abstract val foo: Property<String>
}
val bar by tasks.registering
val baz by tasks.registering(MyTask::class) {
    foo = bar.map {
        println("Calculating foo")
        ""
    }
}

the value of

foo

should not be serialized to the CC entry, as it has a task dependency. But obviously I forgot some detail. 😕

I enabled configuration cache in my library, but for some reasons tests started failing and hanging indefinitely, so I disabled it just for the test tasks. What's the best way to debug the issue? I made a PR re-enabling configuration cache for the tests that show the failure. https://github.com/eygraber/sqldelight-androidx-driver/pull/92 Here's a scan of a failed run - https://scans.gradle.com/s/z5i2jptjvqmlg

I implement a build cache service which needs credentials for the operation. It looks like credential change invalidates configuration cache entry:

Calculating task graph as configuration cache cannot be reused because environment variable 'AWS_ACCESS_KEY_ID' has changed.

Is there a way to avoid configuration cache invalidation when credentials change?

Should we still recommend to users to write

val theirTask by tasks.registering {
    aProperty = provider { someComplexInitialization() }
}

instead of

val theirTask by tasks.registering {
    aProperty = someComplexInitialization()
}

? With the configuration cache enabled, the task will be configured eagerly anyway if

theirTask

is in the task graph, so the

provider {}

does nothing. Or is

provider {}

only for declaring things outside of tasks?

I have a question related to composite builds and configuration on demand. When you have a project that has a composite build (using includeBuild), it seems that configuration occurs on the composite build even when not referenced as a dependency in the root project. When not using a composite build and just including the projects (using include) it seems to be able to avoid some of the configuration. I'm still investigating this, but is this the case?

I've been trying to improve my configuration cache hits - I noticed that an env var used in a Sync task was busting the cache every time. I've got a version which doesn't bust the cache, but it's pretty noisy. Wondering if anyone can suggest a better solution?

Good morning chat, been a while. How exactly does Gradle instantiate objects when re-using configuration cache? Does it create them using

ObjectFactory#newInstance

(or whatever the internal version of that is) with service injection support or does it try to build the class raw using the saved values. Asking because I am using a transient private field that stores an instance of

Problems

which is normally provided through service injection in constructor parameter or bean getter.

Hi everyone Does anyone know if you can pre-generate configuration-cache for a task (

test

for example) without actually running it?

Hi! I'm seeing a configuration cache crash but I don't understand it.

Exception in thread "DefaultSharedObjectDecoder reader thread" org.gradle.api.GradleException: Could not load the value of 
  field `collection` of `kotlin.collections.builders.SerializedCollection` bean found in 
  field `_byTask` of `org.jetbrains.kotlin.gradle.targets.js.nodejs.TasksRequirements` bean found in 
  field `tasksRequirements` of `org.jetbrains.kotlin.gradle.targets.js.npm.resolver.KotlinCompilationNpmResolution` bean found in 
  field `byCompilation` of `org.jetbrains.kotlin.gradle.targets.js.npm.resolved.KotlinProjectNpmResolution` bean found in 
  field `v` of `java.util.Collections$SingletonMap` bean found in field `projects` of `org.jetbrains.kotlin.gradle.targets.js.npm.resolved.KotlinRootNpmResolution` bean found in 
  field `__resolution__` of `org.jetbrains.kotlin.gradle.targets.js.npm.KotlinNpmResolutionManager$Parameters_Decorated` bean found in Gradle runtime.
	at org.gradle.internal.serialize.graph.BeanPropertyExtensionsKt.readPropertyValue(BeanPropertyExtensions.kt:70)
	at org.gradle.internal.serialize.beans.services.BeanPropertyReader.readFieldOf(BeanPropertyReader.kt:93)
…
Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 53 out of bounds for length 4
	at org.gradle.internal.serialize.codecs.core.jos.JavaObjectSerializationCodec.decode(JavaObjectSerializationCodec.kt:299)
	at org.gradle.internal.serialize.graph.codecs.BindingsBackedCodec.decode(BindingsBackedCodec.kt:92)

* What went wrong:
Could not load the value of field `__npmResolutionManager__` of task `:jsPackageJson` of type `org.jetbrains.kotlin.gradle.targets.js.npm.tasks.KotlinPackageJsonTask`.

No build scan was generated, even though they are enabled. From what I can tell, this was introduced by this commit, but I don't understand why.