-
Notifications
You must be signed in to change notification settings - Fork 508
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
🌱 Move docker build checks to ko #1214
Conversation
Integration tests failure for 861ff865f93fec7c88070e5bcc36733340266151 |
Integration tests failure for 95a662aa6dda8d7842e34e10cbff9cda27c04e28 |
95a662a
to
5b92170
Compare
Integration tests success for 5b921704f37166c1b20ab6b0ad8a11c3a838a863 |
Integration tests success for 462930effc75cac4d3d943476641d5c81cbcc22a |
462930e
to
ea3c5ea
Compare
Integration tests success for ea3c5ea9788893dbb8919c5e7300a622addf6d75 |
Integration tests success for 84199e608e101f09824863a27ec93765c2d484cc |
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.
Thanks @naveensrinivasan !
Move the docker builds checks to ko
84199e6
to
5350611
Compare
Integration tests success for 5350611d1f5541c564b06c69e59e2dd74fe35869 |
Integration tests success for ec92147505919f30161f0f9845355da4d67261a2 |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Move the docker builds checks to ko. Part of moving to Feature: Use
google/ko
instead ofDockerfile
#744Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
None