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

CNF-16121: Backport cluster-compare templates to 4.17 #79

Conversation

lack
Copy link
Member

@lack lack commented Dec 11, 2024

Signed-off-by: Jim Ramsay [email protected]

@openshift-ci-robot
Copy link
Collaborator

@lack: This pull request references CNF-16121 which is a valid jira issue.

In response to this:

Signed-off-by: Jim Ramsay [email protected]

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 openshift-eng/jira-lifecycle-plugin repository.

@lack lack force-pushed the cluster-compare-backport-4.17 branch 3 times, most recently from 6d5993d to 40cc15d Compare December 11, 2024 16:43
ci-validate: check-reference

# Basic lint checking
lintCheck:
Copy link
Member

Choose a reason for hiding this comment

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

In 4.18 we call this from ci-validate, right? is there a reason the 4.17 does not?

Copy link
Member Author

Choose a reason for hiding this comment

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

Correct. In 4.17 we have the infrastructure to call it, but not the changes @imiller0 made to make the yaml files complaint. So enabling this, without also backporting those changes, would make the CI fail.

Copy link
Member Author

Choose a reason for hiding this comment

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

Added a comment to explain this :)

@lack lack force-pushed the cluster-compare-backport-4.17 branch from 40cc15d to 69e07c9 Compare December 18, 2024 12:24
Copy link
Member

@MarSik MarSik 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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 10, 2025
Copy link

openshift-ci bot commented Jan 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lack, MarSik

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 10, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 78ccfed into openshift-kni:release-4.17 Jan 10, 2025
1 check passed
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.

3 participants