tilt-dev / tilt-dev/tilt

get debug info on what `tilt ci` is waiting on

Open
#4,298 1 comment 2 reactions 0 assignees View on GitHub

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

Tory from K8s Slack > #tilt says: I'm running into an issue and don't know how to debug it. I'm trying to run tilt ci on my helm-chart that contains a dependency chart. Even though a k get pods shows everything as healthy and happy, tilt is still running. Is there a command I can run or an output I can look at to see what tilt is waiting for before marking my tilt ci as successful or failed?

Current Behavior

Only visible status is that tilt ci is still waiting, with no further details on why.

Why Do You Want This?

Make it easier to debug tilt ci

Tilt: v0.18.10, built 2021-02-19
System: darwin-amd64
---
Docker (cluster)
- Host: tcp://127.0.0.1:55066
- Version: 1.41
- Builder: 2
---
Docker (local)
- Host: Error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
---
Kubernetes
- Env: minikube
- Context: minikube
- Cluster Name: minikube
- Namespace: default
- Container Runtime: read-failure
- Version: v1.18.3
- Cluster Local Registry: none
---

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the tilt ci command and its current waiting behavior; the issue does not name specific files or tests. Determine what status information is available while tilt ci waits, then make the pending condition visible through command output or another documented diagnostic path.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, helm, kubernetes
Domain
cli, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.