-
Notifications
You must be signed in to change notification settings - Fork 694
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 'digest' field to PushInfo provider. #591
Conversation
containing the to-be-published image digest.
Hi @ceason. Thanks for your PR. I'm waiting for a bazelbuild member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
change looks good overall, but we need tests, and I just noticed we have no tests at all for container_push. I'll figure out hot to add a generic test for container_push
that you can then extend. However, to test this PR, I think the easiest path is to make the image_digest
an explicit output of container_push
so that we can do bazel build <some container_push target>
and then check that the output digest file was produced with some expected values with a file_test
. I'll get back in a bit once I figure out how to best add a test for container_push
, but you can get started on making the file an output.
Also, please ignore the buildkite failures, there's an upstream issue with buildkite that is impacting all bazelbuild projects which should be fixed soon. |
created #595 to add a test |
Test for |
Thanks, I've added the named output and should be able to get to the test a bit later today or some time tomorrow. |
Thanks, setting up the test should not be hard, let me know if you run into issues or have questions. |
I've added a |
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 for adding the test, surprisingly, it passed on BuildKite CI (I was expecting this to fail as I thought we needed to explicitly start up the local registry, but looks like it just works as it is, so I can remove the e2e test I added in an upcoming PR)
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ceason, nlopezgi If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
This fixes bazelbuild#609. Also added end to end test to verify bundle pusher and regular pusher upload legal images.
This fixes bazelbuild#609. Also added end to end test to verify bundle pusher and regular pusher upload legal images.
This fixes bazelbuild#609. Also added end to end test to verify bundle pusher and regular pusher upload legal images.
This PR adds a 'digest' field to PushInfo provider. The field's value is a
<File>
containing the to-be-published image digest.I rearranged the
container_pusher
implementation function a bit, to emphasize that the digester needs to receive the same arguments as the pusher.