Skip to content

Conversation

@YuviGold
Copy link
Contributor

@YuviGold YuviGold commented Nov 4, 2020

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.

@romfreiman
Copy link

@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.
@YuviGold YuviGold force-pushed the e2e-metal-assisted-to-installer-and-cvo branch from 540ef8a to f0d68be Compare November 4, 2020 22:19
@YuviGold
Copy link
Contributor Author

YuviGold commented Nov 5, 2020

/retest

Copy link
Contributor

@vrutkovs vrutkovs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 5, 2020
@sdodson
Copy link
Member

sdodson commented Nov 5, 2020

/approve

@openshift-ci-robot
Copy link
Contributor

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 5, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit b2286c7 into openshift:master Nov 5, 2020
@openshift-ci-robot
Copy link
Contributor

@YuviGold: Updated the following 3 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-version-operator-master.yaml using file ci-operator/config/openshift/cluster-version-operator/openshift-cluster-version-operator-master.yaml
    • key openshift-installer-master.yaml using file ci-operator/config/openshift/installer/openshift-installer-master.yaml
  • job-config-master configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-cluster-version-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-version-operator/openshift-cluster-version-operator-master-presubmits.yaml
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
  • job-config-master configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-cluster-version-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/cluster-version-operator/openshift-cluster-version-operator-master-presubmits.yaml
    • key openshift-installer-master-presubmits.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-master-presubmits.yaml
Details

In response to this:

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.

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.

wking added a commit to wking/openshift-release that referenced this pull request Dec 8, 2020
… 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
wking added a commit to wking/openshift-release that referenced this pull request Jan 24, 2022
…-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/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants