Logs in `imagebuild` will be clean up in prebuild page once it failed
Open
Nobody has claimed this yet.
meta: never-stale
team: webapp
type: bug
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
Logs in imagebuild will be cleaned up on prebuild page once it fails, and then left a blank log for users.
We should left fail logs here to let users know that what is the reason that build failed.
| imagebuild failed only | imagebuild failed in prebuild page |
|---|---|
 |
 |
Steps to reproduce
- Create a repo that with a wrong
.gitpod.Dockerfileand set it as image in.gitpod.yml - Open repo with gitpod, this will show imagebuild failed
- Create a project for this repo
- Open repo with gitpod, this will show prebuild failed
And logs of imagebuild will be cleaned up after it failed
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
Reproduce the failure using a wrong .gitpod.Dockerfile configured through .gitpod.yml, then compare imagebuild-only and prebuild failure behavior. Trace how imagebuild logs are handled after a prebuild fails; done means the failure logs remain visible on the prebuild page instead of being replaced by a blank log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100