ci-operator/jobs/openshift/cluster-version-operator: Metal optional on 4.8 and 4.9#19513
Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom Jun 21, 2021
Conversation
…n 4.8 and 4.9 Just like we did for 4.7 in 23982da (ci-operator/jobs/openshift/cluster-version-operator: Metal optional on 4.7, 2021-03-26, openshift#17203), but now for 4.8 and 4.9. Using the previous procedure on the new releases: $ disp() { > yaml2json < "ci-operator/jobs/openshift/cluster-version-operator/openshift-cluster-version-operator-${1}" | jq -r '.presubmits | to_entries[].value[] | .context + " " + (.always_run | tostring) + " " + (.optional // "-" | tostring)' | sort > } $ diff -U0 <(disp master-presubmits.yaml) <(disp release-4.8-presubmits.yaml) --- /dev/fd/63 2021-06-21 12:20:23.738355653 -0700 +++ /dev/fd/62 2021-06-21 12:20:23.739355653 -0700 @@ -4 +4 @@ -ci/prow/e2e-metal-assisted false true +ci/prow/e2e-metal-assisted true - And similarly for 4.9, but this commit fixes both.
openshift-ci
Bot
added
the
approved
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LalatenduMohanty, wking 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 |
Contributor
|
@wking: Updated the following 2 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. |
wking
added a commit
to wking/openshift-release
that referenced
this pull request
Jul 14, 2021
…operties As discussed in e6b339e (ci-operator/jobs/openshift/cluster-version-operator: Metal optional on 4.8 and 4.9, 2021-07-21, openshift#19513) and similar work, the current branch-forking procedure does not track these job properties which are not covered by ci-operator/config/... entries. This script makes it easier to mass-repair suspect branches, based on agreement between master and more reliable sibling branches.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just like we did for 4.7 in 23982da (#17203), but now for 4.8 and 4.9. Using the previous procedure on the new releases:
And similarly for 4.9, but this commit fixes both.