Skip to content

Conversation

@rauhersu
Copy link
Contributor

@rauhersu rauhersu commented Oct 29, 2025

Backport from 4.21

@rauhersu rauhersu changed the title Release 4.18.opm.rendering Introduce 'run-opm-command' in the fbc pipeline Oct 29, 2025
@rauhersu
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 29, 2025
@rauhersu rauhersu force-pushed the release-4.18.opm.rendering branch from 30e832d to 69945fc Compare October 29, 2025 13:19
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 5, 2025
@rauhersu rauhersu force-pushed the release-4.18.opm.rendering branch 2 times, most recently from 663d146 to f44c990 Compare November 5, 2025 17:15
@rauhersu
Copy link
Contributor Author

rauhersu commented Nov 5, 2025

/retest

@rauhersu rauhersu force-pushed the release-4.18.opm.rendering branch from f080fb6 to c77a1d1 Compare November 6, 2025 12:51
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 13, 2025
@rauhersu rauhersu force-pushed the release-4.18.opm.rendering branch from 44b67ec to 22b3ca7 Compare November 13, 2025 11:55
@red-hat-konflux
Copy link
Contributor

Caution

There are some errors in your PipelineRun template.

PipelineRun Error
fbc-pipeline.yaml yaml validation error: line 268: could not find expected ':'

@rauhersu rauhersu force-pushed the release-4.18.opm.rendering branch 3 times, most recently from bf39f3d to 1249e68 Compare November 13, 2025 19:31
@fontivan
Copy link
Collaborator

/approve
/lgtm

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

openshift-ci bot commented Nov 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fontivan

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 Nov 14, 2025
@rauhersu rauhersu force-pushed the release-4.18.opm.rendering branch from 1249e68 to 8c80811 Compare November 14, 2025 15:56
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 14, 2025
@fontivan
Copy link
Collaborator

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 14, 2025
@rauhersu rauhersu force-pushed the release-4.18.opm.rendering branch from 8c80811 to acbbd3e Compare November 21, 2025 13:18
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2025
@openshift-ci
Copy link

openshift-ci bot commented Nov 21, 2025

New changes are detected. LGTM label has been removed.

@rauhersu rauhersu changed the title Introduce 'run-opm-command' in the fbc pipeline CNF-20552: [TALM 4.18] : New opm render mechanism for hermetic builds Nov 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 21, 2025

@rauhersu: This pull request references CNF-20552 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 sub-task to target the "4.18.z" version, but no target version was set.

In response to this:

Backport from 4.21

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.

@rauhersu
Copy link
Contributor Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 21, 2025
@rauhersu
Copy link
Contributor Author

/assign @fontivan

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants