autonomousapps / autonomousapps/dependency-analysis-gradle-plugin
Shrink size of outputs on disk
- Dominant language
- Kotlin
- Stars
- 2.2k
- Forks
- 158
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 46
Description
This is a little thing, but our project's combined `build` directories are up to 500 MB - of which 450 MB are `build/reports/dependency-analysis` directories (and 40 MB is the assembled app including libraries). I have a docker build, which returns the `build` directories to the host system if the build fails, and it seems docker struggles when that directory gets much over 500 MB.
Not sure what if anything can be done about it? I could probably filter them out.
Contributor guide
Research direction
The issue names the generated build/reports/dependency-analysis directories and the assembled app, but no source file or test. Start by locating what creates those outputs and reproduce the failed Docker build; done means reducing the build-directory size without removing required reports or the assembled app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100