gradle / gradle/develocity-build-validation-scripts
Use a consistent user-level cache directory instead of installation-relative paths
- Dominant language
- Shell
- Stars
- 115
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
Currently, BVS stores its data relative to the installation directory. With one installation this is fine, but with multiple installations it can lead to multiple data directories scattered across the machine. This makes disk space management more challenging as there can be multiple, large data directories present on the machine in different places, rather than one well-known place.
Related to #640
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating where BVS derives its installation-relative data path, then read the context in related issue #640. Done means all installations use one consistent user-level cache directory instead of scattering data across installation locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100