artifact caching based on dependencies
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Currently, Tilt relies heavily on Docker build caching.
But even if a docker build is completely cached, you still pay the overhead cost of tarring up the build context and sending it.
One nice feature of Skaffold I admire is that they compute the hash of a workspace, and skip the build if it matches a previous hash.
This might be a nice addition to Tilt
One thing I dislike about Skaffold's implementation is that it's a purely-local feature, and wonder how a Tilt implementation might interoperate better with remote builds, so you can better share cache results between users (as in https://github.com/tilt-dev/tilt/issues/3629)
Contributor guide
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
No source files or tests are named. Start by tracing Tilt's Docker build and caching flow, then review issue #3629 for the remote-cache context. Done would require a defined workspace/dependency hash that avoids sending unchanged contexts and an approach for sharing cache results between users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100