Updating operator-registry builder & base images to be consistent with ART #471
Conversation
|
/ok-to-test we should double check that the cross-compilation tooling is still available in these images |
openshift-ci-robot
added
the
ok-to-test
|
@jupierce: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
openshift-ci-robot
added
triage/unresolved
|
Obsoleted by #516 |
|
@yselkowitz: You can't close an active issue/PR unless you authored it or you are a collaborator. 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/test-infra repository. |
|
/close |
|
@dinhxuanvu: Closed this PR. 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/test-infra repository. |
Updating operator-registry builder & base images to be consistent with ART
Reconciling with https://github.com/openshift/ocp-build-data/tree/f66c03011773dc3755ad874fc691be612914d65f/images/operator-registry.yml
If you have any questions about this pull request, please reach out to
@art-teamin the#aos-artcoreos slack channel.Depends on openshift/images#44 . Allow it to merge and then run
/test allon this PR.