Nikolay Metchev

What would be even better is if NpmTask were cached as well. Should I open a different issue?

is there an issue for symlinks support in the gradle cache that we can vote on?

Thanks @Flarna but it does feel like we need a new issue to make NpmTask cacheable.

@JamesXNelson I attempted to use your workaround but I can't seem to get `yarn_install` to be cacheable Here is what I put in my build.gradle. If I use `--scan` it...

Nevermind. I have a solution now: ``` yarn_install { inputs.file('package.json').withPathSensitivity(PathSensitivity.RELATIVE) outputs.dir('node_modules') if (System.getenv("CI") != null) { args = ['--frozen-lockfile','--no-bin-links'] } else { args = ['--no-bin-links'] } outputs.upToDateWhen { true }...

> If you use the preconfigured yarn install task from the fork I think it should work out-of-the-box Which fork?

Debian JDK is what distroless uses. We were very happy with it, but for some reason they don't keep up with security updates. Perhaps they don't have enough resources. For...

Please find attached a reproducer. If you run ``` ./gradlew clean pitestReportAggregate --no-configuration-cache --no-build-cache ``` It will only aggregate the common project and not the alerts-core project. [messaging-pitest-bug.tar.gz](https://github.com/szpak/gradle-pitest-plugin/files/12027154/messaging-pitest-bug.tar.gz)

Any news here?

@szpak any luck with a proper fix?