chore: update to new script name, which doesn't need CI_CHE_OPERATOR_IMAGE passed into it anymore (https://github.com/eclipse/che/issues/21836)

[nickboldt]

chore: update to new script name, which doesn't need CI_CHE_OPERATOR_IMAGE passed into it anymore

New script: https://github.com/eclipse-che/che-operator/commits/main/build/scripts/olm/test-catalog-from-sources.sh
Old script: https://github.com/eclipse-che/che-operator/blob/7.56.x/build/scripts/olm/testCatalogFromSources.sh

re: eclipse-che/che#21836

[openshift-ci]

Hi @nickboldt. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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]

@nickboldt: the following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-eclipse-che-che-operator-main-v11-devworkspace-happy-path	eclipse-che/che-operator	presubmit	Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse refresh to get an updated list of affected jobs (useful if you have new pushes to the branch)

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[flacatus]

/ok-to-test

[tolusha]

Sounds good

[flacatus]

/lgtm

[nickboldt]

So how do we make this mergeable?

[tolusha]

/rehearsals-ack

[tolusha]

/lgtm

[tolusha]

/ok-to-test

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flacatus, nickboldt, tolusha

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:

• ci-operator/config/eclipse-che/che-operator/OWNERS [flacatus,tolusha]

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

[openshift-ci]

@nickboldt: all tests passed!

Full PR test history. Your PR dashboard.

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.

[flacatus]

/rehearsals-ack

[rhopp]

/pj-rehearse ack

[openshift-ci]

@nickboldt: Updated the ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:

• key eclipse-che-che-operator-main__v11.yaml using file ci-operator/config/eclipse-che/che-operator/eclipse-che-che-operator-main__v11.yaml

In response to this:

chore: update to new script name, which doesn't need CI_CHE_OPERATOR_IMAGE passed into it anymore

New script: https://github.com/eclipse-che/che-operator/commits/main/build/scripts/olm/test-catalog-from-sources.sh
Old script: https://github.com/eclipse-che/che-operator/blob/7.56.x/build/scripts/olm/testCatalogFromSources.sh

re: eclipse-che/che#21836

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.