Skip to content

Conversation

@lwan-wanglin
Copy link
Member

@lwan-wanglin lwan-wanglin commented Oct 29, 2025

I’m trying to build a per-branch catalog in Prow and have started by adding a catalog index Dockerfile to the repository, refer to MULTIARCH-5537

Command to render the Operator bundle and generate YAML entries for the catalog index:
opm render registry.ci.openshift.org/origin/multiarch-tuning-op-bundle:main --output=yaml >> /tmp/index.yaml

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 29, 2025
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Oct 29, 2025

@lwan-wanglin: This pull request references MULTIARCH-5537 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.21." or "openshift-4.21.", but it targets "mto-1.3" instead.

In response to this:

I’m trying to build a per-branch catalog in Prow and have started by adding a catalog index Dockerfile to the repository, refer to MULTIARCH-5537

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 29, 2025
@lwan-wanglin
Copy link
Member Author

/retest

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Nov 3, 2025

@lwan-wanglin: This pull request references MULTIARCH-5537 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.21." or "openshift-4.21.", but it targets "mto-1.3" instead.

In response to this:

I’m trying to build a per-branch catalog in Prow and have started by adding a catalog index Dockerfile to the repository, refer to MULTIARCH-5537

Command to render the Operator bundle and generate YAML entries for the catalog index:
opm render registry.ci.openshift.org/origin/multiarch-tuning-op-bundle:main --output=yaml >> /tmp/index.yaml

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.

@AnnaZivkovic
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 3, 2025
@openshift-ci
Copy link

openshift-ci bot commented Nov 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AnnaZivkovic, lwan-wanglin

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:
  • OWNERS [AnnaZivkovic,lwan-wanglin]

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

@lwan-wanglin
Copy link
Member Author

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 416e85e into outrigger-project:main Nov 4, 2025
29 checks 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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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