Skip to content
This repository has been archived by the owner on Aug 19, 2020. It is now read-only.

Kotlin script caching does not work with Gradle Enterprise remote build cache #1023

Closed
ldaley opened this issue Aug 10, 2018 · 2 comments
Closed

Comments

@ldaley
Copy link

ldaley commented Aug 10, 2018

Expected Behavior

To be able to use our cache.

Current Behavior

Fails with:

Could not load entry build file '«script»' from remote build cache: Loading entry from 'https://«host»/cache/gradle-kotlin-dsl/dx7phw87epyvb7zje5dti3tvl' response status 400: Bad Request

The problem is that gradle-kotlin-dsl/dx7phw87epyvb7zje5dti3tvl is rejected as a cache key. The GE build cache expects keys to be [a-z0-9]{1,128}. We could lift this restriction, but I think it would be better to change the key format that Kotlin is using here.

Steps to Reproduce (for bugs)

Just try to use it on gradle/gradle, with access to the Gradle Inc. cache instance enabled.

@mark-vieira
Copy link

FWIW, relaxing this restriction would likely be significantly complicated in a multi-node replication scenario running different versions of controller/nodes.

+1 on just aligning the cache key produced.

@bamboo
Copy link
Member

bamboo commented Aug 10, 2018

Fixed in 438c2e1 by discarding the gradle-kotlin-dsl/ cache key prefix.

@bamboo bamboo closed this as completed Aug 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants