E3SM-Project / E3SM-Project/containers
optimize building recipes with reusing caching
- Dominant language
- Dockerfile
- Stars
- 4
- Forks
- 4
- Avg merge
- 14h 7m
- Merged PRs (30d)
- 9
Description
We could utilize preexiting spack cache instead of rebuidling every little thing. Building cmake alone is a total monster of a job. :)
Example of how to do it, but there are others, and this could easily be an issue for claudio
https://github.com/E3SM-Project/containers/blob/a54261dd797f872f1d1ed7d8bd1cd6bff6bc766b/ghci/Dockerfile#L80-L96
cc @bartgol
_Originally posted by @mahf708 in https://github.com/E3SM-Project/containers/issues/40#issuecomment-5465795779_
Contributor guide
Research direction
Start with the referenced ghci/Dockerfile lines 80-96 and compare its cache usage with the container recipes in this repository. Identify which recipes rebuild dependencies unnecessarily; done means they reuse the available Spack cache and avoid rebuilding components such as CMake.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, dockerfile
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100