kpack icon indicating copy to clipboard operation
kpack copied to clipboard

Lack of the way to distinguish the user error in a build

Open allxiao opened this issue 4 years ago • 0 comments

Currently, we do not have a stable way to distinguish the user error in a build (e.g., broken source, invalid dependency configuration, etc.). And because the build process is hidden in kpack, it's difficult to analyze the build output to decide if this is caused by the kpack infra failure (e.g., network broken, pod eviction) so we need to improve the stability and probably retry automatically, or it's caused by user error and we will never succeed so we need to inform the user to improve their code and retry manually.

This should be a general issue and probably some SDK / tools may help.

allxiao avatar Jul 13 '20 01:07 allxiao