gradle / gradle/common-custom-user-data-gradle-plugin
Develocity and this plugin should avoid reading env variables during configuration time
- Dominant language
- Java
- Stars
- 63
- Forks
- 31
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 9
Description
Develocity and this plugin should avoid reading env variables during configuration time. As far as I can tell these are only needed for reporting and not actual configuration. As is, any change to these env variables will invalidate configuration cache. Ideally you read these env variables later or via providers API.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are identified in the issue. Inspect the plugin's configuration-time handling of Develocity and environment variables, then trace which values are only needed for reporting; verify the result with Gradle configuration-cache checks and confirm that changing those variables no longer invalidates the cache.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100