Gabriel Feo
03/08/2023, 7:24 PMcacheIf { !isCI }
but that means developers will have to build it locally, which may or may not be an issuemelix
03/15/2023, 8:41 AMSebastian Kacprzak
03/23/2023, 5:57 PMInput (...) is in both builds but the values are different.
(both build scans were with capture { taskInputFiles = true })Jakub Chrzanowski
03/24/2023, 4:37 PMColton Idle
04/02/2023, 9:12 AMSatyarth Sampath
04/03/2023, 12:40 PMbuild-cache-1
) and the modules(modules-2/files-2.1
) cache directories?
My use-case is that I want to share the module cache across multiple gradle instances but have exclusive build-cache directories for each of the running gradle instances. This is because I currently run multiple gradle instances on the same machine.Ivan Alvarado
04/13/2023, 6:56 PMkapt
tasks will enter corrupted cache entries (generated files) into our cache nodes. These files sometimes are kapt generated stub files that have error.NonExistentClass
annotations for the classes that, we presume, were not generated due to the premature stop.
Thus, we're wondering if there's a way to tell Gradle to hold off on publishing cache entries until the build was successful?Ben Boral
05/03/2023, 11:30 PMNon-cacheable because 'Task outputs cacheable' not satisfied [ENABLE_CONDITION_NOT_SATISFIED]on all my link steps (for example
linkReleaseFrameworkIosArm64
). Wondering if this has to do with the multiplatform gradle plugin and it affects everyone or if it's just my project.John
05/15/2023, 9:14 PMJohn
05/17/2023, 2:41 PMAkhil Vaidya
05/22/2023, 12:26 PMBobby Hargett
06/07/2023, 3:55 PMVladimir Prus
06/29/2023, 7:37 PMCesar Morigaki
07/14/2023, 12:58 PMkotlinJavaToolchainProvider
input cache key differs
Is there a way to print kotlinJavaToolchainProvider
? Any other ideias to check why this is different?Mattia
08/10/2023, 9:30 AMoutputs.upToDateWhen { outputs.files.files.all { it.exists() } }
But I wonder, how is this not automatic? How can a task be considered up to date if it didn’t even generate the files? I hope that knowing this might help me identify a proper solution or report a better bug to the Kotlin team.Kengo TODA
09/16/2023, 8:24 AMFileCollectionBackedArchiveTextResource
instance.
I supposed the Hashable
interface does this trick but could not find the implementation handling the TextResource
nor FileCollection
interface.
If you know, please help me to find the code calculating build cache key for TextResource
. Thanks in advance!ritesh singh
10/01/2023, 3:19 AMandroid.jar
as an input.
Wondering, if it's a known issue. Initially i thought, it must be just kapt
realted task, but i noticed it being a reasons for cache-miss for JavaCompile
task as well.Charbel Sadaka
11/09/2023, 12:48 PMRonanb Browne
11/16/2023, 12:08 PMVladislav Yundin
11/23/2023, 9:45 AMmelix
12/04/2023, 9:42 AMRegularFileProperty
as an input, which is a .properties
file, and it seems that the timestamp in that properties file is relevant to caching.Eug
01/18/2024, 3:30 PMMarcin Robaczyński
02/08/2024, 1:32 PMbuild-conventions
project fully cache'able?
I'm running into a problem where configuration has to re-run on CI due to:
Calculating task graph as configuration cache cannot be reused because an input to plugin 'org.gradle.groovy-gradle-plugin' has changed.
Happens when I cache and restore build-conventions/build/*
files. Is there an easy way to verify what are groovy-gradle-plugins' input?Roded Bahat
02/22/2024, 2:15 PM-Dorg.gradle.caching.debug=true
and comparing two builds' Build Scans shows that the only difference between the executions is the location of some of the dependencies.
I.e., in one build, some dependencies where fetched from /data/gradle-dependency-cache/gradle-home
while in the other, they were fetched from /home/jenkins/.gradle
.
The hashes for all dependencies are exactly the same between the builds, regardless of which folder they were fetched from.
And yet, Gradle calculated a different input file fingerprint for jar list input.
Can anyone explain what's going on here and how I might be able to solve this issue so that this task would be deterministically cached?
I can share the task logs if that would be of any help.
Thanks a lot.Andrea Di Menna
03/01/2024, 11:36 AMWriteProperties
task which seems to be not restored from the build cache. This happens not consistently.
I get
> Task :gradle-plugins:config-gradle-plugin:props FROM-CACHE
Appending implementation to build cache key: org.gradle.api.tasks.WriteProperties_Decorated@7f188f326239382116310befb40da15f
Appending additional implementation to build cache key: org.gradle.api.tasks.WriteProperties_Decorated@7f188f326239382116310befb40da15f
Appending input value fingerprint for 'comment' to build cache key: f6bd6b3389b872033d462029172c8612
Appending input value fingerprint for 'encoding' to build cache key: a01a9ddf322da930e94b377f84683032
Appending input value fingerprint for 'lineSeparator' to build cache key: d0608bef942477d145a034e0902d2ff8
Appending input value fingerprint for 'properties' to build cache key: 3a19c1074096c79765360687c2843f48
Appending output property name to build cache key: destinationFile
Build cache key for task ':gradle-plugins:config-gradle-plugin:props' is 3edb56921b5aba38b2f0c0e8e1ab8a9a
but then there is no such file in the directory where it should be restored.
This does not happen with Gradle 8.5
Do you have any hints to follow?Slackbot
03/12/2024, 11:14 AMJavi
03/19/2024, 2:43 AMOverlapping outputs: Gradle does not know how file 'CHANGELOG.md' was created (output property 'outputFile'). Task output caching requires exclusive access to output paths to guarantee correctness (i.e. multiple tasks are not allowed to produce output in the same location).
The problem is one task is adding some lines to the changelog file, and another different task formats the changelog file.
Is it not a valid use case? Should I open an issue?
What if two different plugins use the changelog file? It would be impossible to make a task cacheable.Sergey Lapin
03/27/2024, 8:23 AMDaniel Torrescusa
04/03/2024, 5:29 PMMarcin Laskowski
04/19/2024, 4:57 PMbuild/intermediates/lint_model/debug/debug_artifact_libraries.xml
:
<libraries>
<library
name="androidx.annotation:annotation-jvm:1.6.0@jar"
jars="/Users/marcin.laskowski/.gradle/caches/modules-2/files-2.1/androidx.annotation/annotation-jvm/1.6.0/a7257339a052df0f91433cf9651231bbb802b502/annotation-jvm-1.6.0.jar"
resolved="androidx.annotation:annotation-jvm:1.6.0"
provided="true"/>
....
</libraries>
The question is, are paths to gradle cache folder even supported in this kind of files? Can this be the root cause of poisoned cache?