Different logging options for tilt ci logs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
Ability to have tilt ci log output for each stage to a file and save as an artefact
Current Behavior
tilt ci will just log to a console
Why Do You Want This?
We are using Tilt for our integration tests and system tests, and we love how we have a consistent build across developers working locally, as well as how the tests run in the CI. We have roughly ten apps, all of which are quite verbose in their logging. We find debugging within the pipeline quite challenging, and the logs are too large for GitLab, which often results in slow page loading. It would be great to have these logs saved in separate text files and be able to view them as an artefact as needed, or maybe even save them as an HTML page similar to how the local UI looks for even easier viewing
Additional context
Add any other context or screenshots about the feature request here.
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 with the tilt ci command and its current console logging behavior. Clarify whether the feature should produce per-stage text artifacts, an HTML report, or configurable output before identifying the implementation and tests. Done means an agreed output design is implemented and verified for CI use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100