Show output of cached build steps
- Dominant language
- Python
- Stars
- 562
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
Sometimes the build steps break without any exit code. The image layers linked to these steps are then cached and used for other unsuspecting builds.
We can debug the issue with the original build using the output/error. The builds that use the cache, however, can't be debugged.
Fix this by copying the output/error from the deploy candidate that originally built the cached layer.

Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests; start by tracing cached build-step handling and the deploy candidate data that stores output and errors. Confirm how cached layers are reused, then verify that builds using them display the original deploy candidate's output/error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100