-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add e2e-metal-assisted to installer and cluster-version-operator #13384
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 e2e-metal-assisted to installer and cluster-version-operator #13384
Conversation
|
@wking so CVO can be tested in assisted flow |
Add an optional e2e-metal-assisted job for installer and cluster-version-operator Generated by manually changing `ci-operator/config/...`, running: ``` $ make update ``` and tuning the configurable always_run and optional fields.
540ef8a to
f0d68be
Compare
|
/retest |
vrutkovs
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
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson, vrutkovs, YuviGold 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 |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@YuviGold: Updated the following 3 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. |
… base_images for 4.6 and later Per Justin, these are now handled implicitly by ci-operator, so removing them reduces the chance that CI builds diverge from ART builds (see also [1]). dev-scripts is from f0d68be (Add e2e-metal-assisted to installer and cluster-version-operator, 2020-11-04, openshift#13384), and is implicitly passed through and then consumed by the baremetalds-packet-setup step and similar, so we need to keep that for 4.7 and later (where we have an e2e-metal-assisted entry in tests). assisted-test-infra is from c11d67d (cluster-version-operator uses openshift-kni/assisted-test, 2020-12-06, openshift#14119), and is consumed by baremetalds-assisted-setup. [1]: https://github.com/openshift/enhancements/blob/master/enhancements/art/flexibly-enforcing-product-build-constraints-in-ci.md
…-assisted presubmits These are descended from f0d68be (Add e2e-metal-assisted to installer and cluster-version-operator, 2020-11-04, openshift#13384), where they were intended to make it easy for folks to evaluate in-flight CVO pull requests vs. assisted-installer CI. However, with the recent '/payload ...' test support [1], we can maintain the job configuration for the release-controller periodics, and run them as needed on component pull requests, without having to maintain per-component presubmit configuration. This commit drops the per-component presubmit configuration to reduce future maintenance work. [1]: https://docs.ci.openshift.org/docs/release-oversight/payload-testing/
Add an optional e2e-metal-assisted job for installer and
cluster-version-operator
Generated by manually changing
ci-operator/config/..., running:and tuning the configurable always_run and optional fields.