In our organisations we have a couple of hundred builds, which are very uniform (thanks to the power of custom gradle plugins). For two of our own artifacts (one which has been static for the past years, the other gets a new version more regularly), about which I can find nothing special, we occasionaly (once every 30 builds or so) get a kind of corrupt cache error. See an abbreviated stacktrace below, and a complete one in the attachment. We are (unfortunately) still on Gradle 2.9. I scanned the release notes for all newer versions, I could not find an indication that my problem is solved.
Is this a known issue, is there something we can try to fix this?
* Exception is: org.gradle.api.artifacts.ResolveException: Could not resolve all dependencies for configuration ':myConfiguration'. [...] Caused by: org.gradle.internal.resolve.ArtifactResolveException: Could not download our.organisation.our.artifact.impl.jar (our.organisation:our.artifact:188.8.131.52-289) [...] Caused by: org.gradle.internal.resource.ResourceException: Could not get resource 'http://our.artifactory.server:28080/artifactory/OUR_REPO/our/organisation/our.artifact/184.108.40.206-289/our.organisation.our.artifact.impl-220.127.116.11-289.jar'. [...] Caused by: org.gradle.api.UncheckedIOException: Could not read entry 'http://our.artifactory.server:28080/artifactory/OUR_REPO/our/organisation/our.artifact/18.104.22.168-289/our.organisation.our.artifact.impl-22.214.171.124-289.jar' from cache artifact-at-url.bin (C:\Users\p5dev\.gradle\caches\modules-2\metadata-2.16\artifact-at-url.bin). [...] Caused by: org.gradle.api.UncheckedIOException: java.io.EOFException [...] Caused by: java.io.EOFException at org.gradle.cache.internal.btree.FileBackedBlock<a class="attachment" href="/uploads/default/original/2X/0/0106fd7200b207145ca61d4b27e17d19e24170ee.zip">completestactrace.zip</a> (2.7 KB)
… 139 more