-
```shell
$ mkdir /tmp/test && cd "$_"
$ gradle init --type java-library --java-version 21 --project-name test --dsl groovy --test-framework junit-jupiter --no-comments --no-incubating --quiet
$ per…
-
### Current Behavior
When using configuration cache and setting a default environment variable in gradle run configuration, gradle caches _all_ envinronment variables and does not invalidate cache wh…
arve0 updated
1 month ago
-
### Preconditions and environment
When you change the contents of the robots.txt file via Content > Design > Configuration > Search Engine Robots, the changes do not become immediately available on…
-
### Current Behavior
given a gradle build using snapshot dependencies (changing dependencies) and configuration cache enabled.
Executing multiple gradle targets will populate the gradle configuration…
-
### Description
Using Gradle 8.2 or newer with stable config cache support, enabling it with org.gradle.configuration-cache=true I'm getting this error:
```
4 problems were found storing the conf…
-
### Describe the bug
No ability to enable configuration cache while using artifactory as well as the fact artifactory makes use of cross configuration killing gains possible by configureondemand Grad…
-
### Description of the bug
With new Gradle 8.6 and the latest [setup-gradle@v3](https://github.com/gradle/actions/tree/v3.0.0/setup-gradle) it is now possible to safely and securely store [Gradle con…
-
### Current Behavior
It feels like there is a race condition somewhere.
[configuration-cache-report.zip](https://github.com/user-attachments/files/17069728/configuration-cache-report.zip)
I get…
-
## Problem
ISMs tend to be pretty static, we can afford to cache ISM configurations for a given address
## Solution
To have fewer RPCs when building metadata, cache ISM configs
-
Requirements for tasks to support configuration caching: https://docs.gradle.org/8.1.1/userguide/configuration_cache.html#config_cache:requirements
Errors logged:
```
FAILURE: Build failed with a…