-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add openshift/build-test-images to tide #18523
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 openshift/build-test-images to tide #18523
Conversation
adambkaplan
commented
May 12, 2021
- Build simples2i image in addition to roots2i image
- Add build-test-images repo to tide, add approve plugin
- Add e2e-aws and e2e-aws-builds suites to tests
- Build simples2i image in addition to roots2i image - Add build-test-images repo to tide, add approve plugin - Add e2e-aws and e2e-aws-builds suites to tests
|
/assign @alvaroaleman |
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.
for the prow config changes
/hold
cancel at your convenience
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan, alvaroaleman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
What benefit is there to adding these images to registry.ci? Since openshift internal registries do not support manifest lists, I'm worried that even if we were to build and push the redhat-developer build multi-arch enabled, if it goes through registry.ci, we'll only get x86 mirrored into openshift/community-e2e-images, and we'll still need a multi-arch override for testing. Why can't the redhat-developer build (with a versioned tag) be mirrored directly without going through registry.ci? |
@yselkowitz adding the images to registry.ci was based on @gabemontero's comment here. We are already pushing the roots2i image, how is the simples2i image any different? How are multiarch images published to quay.io otherwise? |
|
@adambkaplan: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
Yep, following the pattern we started with roots2i (in hindsight, we should have done both when we were in here last time). Among other things, it makes running our e2e in disconnected more seamless. |
|
the failure at https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/18523/rehearse-18523-pull-ci-openshift-build-test-images-master-e2e-aws-builds/1392513319411126272 was the known verify /run based on recent node team changes still catching up on email, but this is mergeable IMO based on manual testing and what we see here with e2e-gcp-builds |
|
/hold cancel /retest |
|
@adambkaplan: Updated the following 8 configmaps:
DetailsIn 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/test-infra repository. |