-
Notifications
You must be signed in to change notification settings - Fork 60
Adding a way to specify a shared image gallery so we can test staging images produced from image-builder before promoting them #528
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
Conversation
… images produced from image-builder before promoting them Signed-off-by: Mark Rossett <marosset@microsoft.com>
|
/hold |
mboersma
left a comment
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
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marosset, mboersma 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 |
|
/test ls |
|
@marosset: The specified target(s) for Use In response to this:
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-sigs/prow repository. |
|
/test pull-e2e-capz-windows-2022-staging-gallery |
|
/test pull-e2e-capz-windows-2022-staging-gallery New gallery images have been published to the staging gallery (previously there were none) |
|
I think we need to scope the *-stagign-gallery jobs to a single region. |
|
/test pull-e2e-capz-windows-2022-staging-gallery |
|
/test pull-e2e-capz-windows-2022-staging-gallery |
|
/hold cancel |
Path of kubernetes-sigs/image-builder#1874