Enable caching feature (avoid unnecessary rebuilds) in Docker builds
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
The first PR introducing the Docker build sets noCache: true in the pipelines. The caching infra requires some setup in dotnet/versions to store persistent information, like https://github.com/dotnet/versions/blob/main/build-info/docker/image-info.dotnet-dotnet-docker-nightly.json.
There's no (known) blocker to getting this set up. (It's fine to store our json file(s) in the same dir.) It wasn't done in the initial implementation because it's an easy candidate to work on incrementally, later.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Docker build pipelines where noCache is set to true, then compare the required setup with dotnet/versions/build-info/docker/image-info.dotnet-dotnet-docker-nightly.json. Done means persistent cache metadata is stored in the agreed directory and Docker builds no longer disable caching unnecessarily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100