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

[WIP] Generate config for INTEROP tests on 4.18 #419

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mgencur
Copy link
Contributor

@mgencur mgencur commented Nov 11, 2024

https://issues.redhat.com/browse/SRVCOM-3401

  • Configuration for a candidate release of OpenShift now has to be specified explicitly. Previously, we generated them automatically by taking the highest version of OpenShift in config, bumping the minor version, and creating the config for the candidate release. Now, we need to be able to specify which custom configs will be run for each version of OpenShift - including this candidate version.
  • Add tests for candidate OCP 4.18 explicitly for all repositories, but only for the latest version Serverless 1.36.
  • Add INTEROP config for OpenShift 4.18. This is supposed to replace manual changes like in this PR: [INTEROP-7533] Expand OCP CI Serverless to OCP 4.18. openshift/release#57252 (it's error prone and requires multiple reviews from our team).
  • Remove older interop tests for OCP <=4.17

When merging this PR, the following config will be generated: openshift/release#58680

Copy link

openshift-ci bot commented Nov 11, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mgencur

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-merge-robot openshift-merge-robot removed the needs-rebase The PR needs to have conflicts fixed label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants