-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add docker build output to task result #805
Conversation
You need a changelog fragment. Will look at the change itself later... |
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.
What about adding some unit/integration tests (eg. here tests/integration/targets/docker_image)?
@raags could you please update your PR? needs_info |
tests/integration/targets/docker_image/tasks/tests/docker_image.yml
Outdated
Show resolved
Hide resolved
tests/integration/targets/docker_image/tasks/tests/docker_image.yml
Outdated
Show resolved
Hide resolved
The build output is only added during failures, but its useful to have this available during normal task execution as well.
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.
LGTM
The build output is only added during failures, but its useful to have this available during normal task execution as well. (cherry picked from commit 33b8d1c)
@raags thanks a lot for contributing this! |
The build output is only added during failures, but its useful to have this available during normal task execution as well. (cherry picked from commit 33b8d1c) Co-authored-by: Raghu Siddarth Udiyar <[email protected]>
SUMMARY
The build output is only added during failures, but its useful to have this available during normal task execution as well.
ISSUE TYPE
COMPONENT NAME
docker_image
ADDITIONAL INFORMATION
This change adds a new key
build_output
to the task result which includes all the docker build steps. This is useful to understand for e.g. what steps were run for the build, as well as steps that used / not used the image cache.