NO-JIRA: Add missing build-args-file to bundle-4-23 pipelines

[pacevedom]

The Konflux auto-generated pipeline files for lvm-operator-bundle-4-23 were missing the build-args-file parameter, causing OPERATOR_VERSION and other build args from release/container-build.args to not be passed to buildah. This resulted in empty version strings and a failed operator-sdk generate bundle call.

Summary by CodeRabbit

• Chores
  • Added CI/CD pipeline configurations for automated building and testing of the lvm-operator bundle on pull requests and push events.

[openshift-ci-robot]

@pacevedom: This pull request explicitly references no jira issue.

Details

In response to this:

The Konflux auto-generated pipeline files for lvm-operator-bundle-4-23 were missing the build-args-file parameter, causing OPERATOR_VERSION and other build args from release/container-build.args to not be passed to buildah. This resulted in empty version strings and a failed operator-sdk generate bundle call.

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 2ffeb9f1-91f0-43a2-a3b6-bc2b72a75d18

📥 Commits

Reviewing files that changed from the base of the PR and between 975cba4 and d3e0f42.

📒 Files selected for processing (2)

• .tekton/lvm-operator-bundle-4-23-pull-request.yaml
• .tekton/lvm-operator-bundle-4-23-push.yaml

---

Walkthrough

Two new Tekton PipelineRun manifests add automated build and publish workflows for the lvm-operator-bundle. The PR pipeline triggers on pull requests; the push pipeline triggers on commits to main. Both configure the same task chain—clone, prefetch dependencies, build image, create index, optionally build source image, run security/scanning tasks, apply tags, push artifacts, and scan RPM signatures—with parameter-driven customization and conditional gating via skip-checks.

Changes

CI/CD Pipelines for lvm-operator-bundle

Layer / File(s)	Summary
PR Build Pipeline .tekton/lvm-operator-bundle-4-23-pull-request.yaml	Tekton PipelineRun for pull-request builds with metadata, build parameters (source, image output, expiration), pipelineSpec (parameters, results, full task chain), optional workspaces (git auth, netrc), and service account configuration.
Push Build Pipeline .tekton/lvm-operator-bundle-4-23-push.yaml	Tekton PipelineRun for push-to-main builds with metadata, build parameters (hermetic, prefetch, caching, SAST targets), pipelineSpec (parameters, results, task chain with conditional security checks), optional workspaces, and service account configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested labels

ready-for-human-review

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding the missing build-args-file parameter to the bundle-4-23 pipelines, which directly addresses the core issue documented in the PR objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR adds only Tekton YAML pipeline configuration files (no Go test code); Ginkgo test naming check is not applicable.
Test Structure And Quality	✅ Passed	PR contains only Tekton YAML pipeline configuration files, not Ginkgo test code. Custom check for test structure/quality is not applicable.
Microshift Test Compatibility	✅ Passed	PR adds only Tekton pipeline YAML files, not Ginkgo e2e tests. MicroShift compatibility check only applies to new test code, making it not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR adds only Tekton PipelineRun YAML files, not Ginkgo e2e tests. The SNO test compatibility check applies only to new e2e tests.
Topology-Aware Scheduling Compatibility	✅ Passed	Added files are Tekton PipelineRun manifests (CI/CD pipelines), not deployment manifests or controllers. They contain no pod scheduling constraints or topology-related directives.
Ote Binary Stdout Contract	✅ Passed	PR adds only Tekton YAML pipeline configuration files, not Go code. OTE Binary Stdout Contract check applies only to process-level code (main(), init(), etc.) in binaries, not declarative YAML.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No Ginkgo e2e tests added. PR only modifies Tekton pipeline YAML files (.tekton/lvm-operator-bundle-4-23-*.yaml) for build infrastructure.
No-Weak-Crypto	✅ Passed	PR adds Tekton YAML pipeline configs with no cryptographic implementations or weak algorithms. SHA256 refs are container image digests only.
Container-Privileges	✅ Passed	No privileged container configurations found; privileged-nested defaults to "false", no securityContext or hostPID/Network/IPC settings present.
No-Sensitive-Data-In-Logs	✅ Passed	Tekton PipelineRun files properly handle secrets via workspaces and don't expose passwords, tokens, keys, or PII in logging or environment variables.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacevedom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [pacevedom]

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

[pacevedom]

/hold

[openshift-ci]

@pacevedom: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.