I see a lot of my CI kotlin compile (maybe all) ar...

# gradle

[Eugen Martynov]

I see a lot of my CI kotlin compile (maybe all) are missing build cache. What can be the cause? (Sorry if it was answered already or there is no answer since information is not enough).

[Eugen Martynov]

Looks like doesn't happen on my local build.

[Trevor Stone]

There isn’t enough information here. Are you using a remote build cache or a local build cache? Is your CI running in a container that gets disposed and recreated each time or is it running on persistent dedicated hardware?

[Eugen Martynov]

It uses only local build cache. CI is running in container, not sure if it is disposed or reused. This is GitHub CI hosted machines.

[Trevor Stone]

Yeah so that is most likely creating a new “clean” container each time, so there is no local cache that is persisted between builds

[Eugen Martynov]

Except, we save and restore .gradle folders between builds

[Eugen Martynov]

This is also end of the day. so only my builds are run after each other. So, I'm pretty sure the cache of previous build should be reused maximum.

[Eugen Martynov]

I have something similar to https://github.com/actions/cache/blob/main/examples.md#java---gradle

[Carter]

It will only use cache from the master branch, or prior builds of the same branch.

[Trevor Stone]

I haven’t use github CI personally, but my guess would be that it isn’t saving this cache correctly after each build, or it isn’t restoring it correctly

[Carter]

This is to prevent a malicious branch from poisoning the cache of other branches.

[Carter]

I don’t recommend saving the entire gradle folder, but being more selective of the dependencies, gradle binary, and gradle cache. This avoids leaking secrets that you might write to ~/.gradle/gradle.properties

[Eugen Martynov]

Carter, it is end of the day

[Eugen Martynov]

So, I'm pretty sure only my branch is executed

[Eugen Martynov]

Just checked log and I see that my jobs are running only

[Eugen Martynov]

I did scan and I see that kotlin compile have the different cache key

[Carter]

This should help: https://docs.github.com/en/actions/advanced-guides/caching-dependencies-to-speed-up-workflows

[Eugen Martynov]

We are using it already 🙂

[Carter]

I find sometimes the cache behavior is mysterious. But if I add another commit to a branch, I do see it applying the cache to that branch.

[Eugen Martynov]

I need to find why the cache key for kotlin compile are different

[Eugen Martynov]

Interesting that they have two different types - one is kotlin compile and one is kotlin compile with workers

[Eugen Martynov]

Aha, I added parallel execution in between, so this might be the cause