Skip to content
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

release: Normalize how release branch jobs pass args to ci-operator #8049

Merged

Conversation

smarterclayton
Copy link
Contributor

This structure is much easier to bulk refactor if ci-operator
arguments change in the future.

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

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 /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 Mar 31, 2020
@smarterclayton smarterclayton force-pushed the normalize_release branch 4 times, most recently from 3993415 to b7915c2 Compare March 31, 2020 18:59
This structure is much easier to bulk refactor if ci-operator
arguments change in the future.
@smarterclayton smarterclayton added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2020
@openshift-merge-robot openshift-merge-robot merged commit e7e60cf into openshift:master Mar 31, 2020
@openshift-ci-robot
Copy link
Contributor

@smarterclayton: Updated the following 12 configmaps:

  • job-config-4.4 configmap in namespace ci at cluster default using the following files:
    • key openshift-release-release-4.4-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.4-periodics.yaml
  • job-config-4.6 configmap in namespace ci at cluster default using the following files:
    • key openshift-release-release-4.6-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.6-periodics.yaml
  • job-config-4.1 configmap in namespace ci at cluster default using the following files:
    • key openshift-release-release-4.1-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.1-periodics.yaml
  • job-config-4.3 configmap in namespace ci at cluster default using the following files:
    • key openshift-release-release-4.3-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.3-periodics.yaml
  • job-config-4.5 configmap in namespace ci at cluster default using the following files:
    • key openshift-release-release-4.5-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.5-periodics.yaml
  • job-config-4.2 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.2-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.2-periodics.yaml
  • job-config-4.4 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.4-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.4-periodics.yaml
  • job-config-4.3 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.3-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.3-periodics.yaml
  • job-config-4.1 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.1-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.1-periodics.yaml
  • job-config-4.6 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.6-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.6-periodics.yaml
  • job-config-4.5 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.5-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.5-periodics.yaml
  • job-config-4.2 configmap in namespace ci at cluster default using the following files:
    • key openshift-release-release-4.2-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.2-periodics.yaml

In response to this:

This structure is much easier to bulk refactor if ci-operator
arguments change in the future.

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.

@openshift-ci-robot
Copy link
Contributor

@smarterclayton: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/promote-release-openshift-okd-machine-os-content-e2e-aws-4.4 c71ec331d0ef4a5018a0949f85a8f9bdfd41ea83 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-old-rhcos-e2e-aws-4.2 39934151a960d9ff6ffe06a0e785a26b5b592a96 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-old-rhcos-e2e-aws-4.3 39934151a960d9ff6ffe06a0e785a26b5b592a96 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.4-nightly-to-4.4-nightly b7915c2e3da0a56b1840b96fc4ccc077a0e0d965 link /test pj-rehearse
ci/rehearse/endurance-e2e-aws-4.4 b7915c2e3da0a56b1840b96fc4ccc077a0e0d965 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.2-to-4.3 b7915c2e3da0a56b1840b96fc4ccc077a0e0d965 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-gcp-upgrade-4.5 b7915c2e3da0a56b1840b96fc4ccc077a0e0d965 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-fips-4.4 b7915c2e3da0a56b1840b96fc4ccc077a0e0d965 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.4-stable-to-4.4-ci b7915c2e3da0a56b1840b96fc4ccc077a0e0d965 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-old-rhcos-e2e-aws-4.4 b7915c2e3da0a56b1840b96fc4ccc077a0e0d965 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.6 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-old-rhcos-e2e-aws-4.6 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.3-to-4.4-to-4.5-to-4.6-ci cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.5-to-4.6 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-gcp-upgrade-4.6 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-azure-upgrade-4.6 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.5-stable-to-4.6-ci cb90a2f link /test pj-rehearse
ci/rehearse/endurance-upgrade-aws-4.4 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-azure-upgrade-4.3 cb90a2f link /test pj-rehearse
ci/rehearse/endurance-upgrade-aws-4.3 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.2 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-azure-upgrade-4.4 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.4 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-fips-4.3 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.2-to-4.3 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.4-to-4.5 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-azure-upgrade-4.5 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.2-nightly-to-4.3-nightly cb90a2f link /test pj-rehearse
ci/rehearse/endurance-e2e-aws-4.3 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.4-to-4.4 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-gcp-upgrade-4.3 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.2-to-4.3-to-4.4-to-4.5-ci cb90a2f link /test pj-rehearse
ci/rehearse/endurance-cluster-maintenance-aws-4.4 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.5 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-gcp-upgrade-4.4 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-to-4.4-nightly cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-nightly cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.1-to-4.2 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.1-stable-to-4.2-ci cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-azure-upgrade-4.2 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-gcp-upgrade-4.2 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.3 cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.4-stable-to-4.5-ci cb90a2f link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-old-rhcos-e2e-aws-4.5 cb90a2f link /test pj-rehearse
ci/prow/pj-rehearse cb90a2f link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

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
3 participants