-
Configuration cache seems to be on track for being marked as stable for 8.1 release of gradle which is not that far away. This feature speeds up gradle a lot, but at the moment this plugin is not comp…
-
## Is your feature request related to a problem? Please describe.
Gradle 7.4 has a new incubating feature for the configuration cache, which can speed up builds. https://docs.gradle.org/7.4/userguid…
-
### Current Behavior
The StandardOutputListener added via logging.addStandardErrorListener will be invoked when errors are logged in a project without the configuration cache enabled, but enabling co…
-
### Expected Behavior
Gradle should provide a clear migration path for plugins using build listeners to use build services, also clarifying whether build services are a replacement of build listeners…
-
### Bug Description
**My current configuration**:
langflow:
image: langflowai/langflow:latest
container_name: langflow
environment:
- LANGFLOW_WORKERS=4
- LANGFLOW_CONFIG_DIR=…
-
I've encountered a configuration cache incompatible issue when using `dockerCompose.exposeAsSystemProperties` inside a `doFirst` block, following the guidance in the [plugin's usage guide](https://git…
-
### Current Behavior
It apperas that contents of a `provider {}` is read during configuration time, even if that provider is only used at execution time, resulting in code inside becoming a key for…
-
Gradle configuration cache requires task state to be round-trip serializable. As outlined at #987, this is a signficant constraint on plugin developers and it slows down the end-user experience of cha…
-
### URL
https://grafana.com/docs/alloy/latest/reference/components/otelcol/otelcol.processor.tail_sampling/#otelcolprocessortail_sampling
### Feedback
Slack discussion: https://raintank-corp.slack.…
-
### 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…