configurable timeouts for `tilt ci` builds and readiness
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
From Leopold Schabel in k8s slack:
basically, we need two timeouts:
- one for building the images, which can legitimately take a long time on a cold cache (say, 30 minutes)
- one for waiting for all resources to be ready (which is much faster, but sometimes a change breaks it and some resource fails to become ready)
that way, we could have separate timeouts with
tilt cifor building images (can take a long time) and running them (if it takes long, it failed to converge and should be killed much quicker than the builds)
Current Behavior
Why Do You Want This?
Additional context
Related to #3783
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
Start at the tilt ci entry point and inspect how build completion and resource readiness are currently timed, then read related issue #3783 for context. Done means tilt ci supports separate configurable timeouts for image builds and readiness waiting, with each timeout applying to the intended phase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100