-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: make BuildError serialisable by Celery in case of retry #641
Conversation
Signed-off-by: SdgJlbl <[email protected]>
/e2e |
End to end tests: ✔️ SUCCESS |
/e2e |
/e2e |
End to end tests: ✔️ SUCCESS Crushed it! |
Signed-off-by: SdgJlbl <[email protected]>
Signed-off-by: SdgJlbl <[email protected]>
Signed-off-by: SdgJlbl <[email protected]>
Signed-off-by: SdgJlbl <[email protected]>
73d83c7
to
51fabaf
Compare
/e2e |
End to end tests: ✔️ SUCCESS Congratulations! |
logs = get_pod_logs(k8s_client, pod_name, KANIKO_CONTAINER_NAME, ignore_pod_not_found=True) | ||
delete_pod(k8s_client, pod_name) | ||
for line in (logs or "").split("\n"): | ||
logger.info(line, pod_name=pod_name) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to log this line by line, rather than as a single JSON line?
(I know the backend logs are supposed to be JSONified but IDK about this)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well spotted, that might be the very reason why we have so many lines of log coming from Kaniko.
I'd be in favour to try adding all in the same log, what do you think @guilhem-barthes ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have much more than a surface-level understanding of substrapp, so feel free to wait for Guilhem's review, but to me this looks very good, many thanks!
(#burncelery?)
Signed-off-by: SdgJlbl <[email protected]>
Description
Workaround for this Celery bug
How has this been tested?
Checklist