Red Hat Konflux update ocm-cli #882
Conversation
Signed-off-by: red-hat-konflux <konflux@no-reply.konflux-ci.dev>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: red-hat-konflux[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @red-hat-konflux[bot]. Thanks for your PR. I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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-sigs/prow repository. |
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
* Add container image build support with hermetic and standard build options - Add make targets 'image' and 'hermetic_image' for building container images - Create hack/build_image.sh for standard podman-based image builds - Create hack/build_hermetic_image.sh for reproducible hermetic builds using hermeto - Update Dockerfile to support both hermetic and non-hermetic build modes - Enable flexible image repository, tag, and name configuration via environment variables * Enable hermetic builds in Tekton CI/CD pipelines - Configure pull request pipeline to use hermetic builds with Go module prefetch - Configure push pipeline to use hermetic builds with Go module prefetch - Add prefetch-input parameter for Go dependency management in both pipelines - Ensure reproducible builds in CI/CD environment
* Add container image build support with hermetic and standard build options - Add make targets 'image' and 'hermetic_image' for building container images - Create hack/build_image.sh for standard podman-based image builds - Create hack/build_hermetic_image.sh for reproducible hermetic builds using hermeto - Update Dockerfile to support both hermetic and non-hermetic build modes - Enable flexible image repository, tag, and name configuration via environment variables * Enable hermetic builds in Tekton CI/CD pipelines - Configure pull request pipeline to use hermetic builds with Go module prefetch - Configure push pipeline to use hermetic builds with Go module prefetch - Add prefetch-input parameter for Go dependency management in both pipelines - Ensure reproducible builds in CI/CD environment * HERMETIC variable name correction
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Note Free review on us!CodeRabbit is offering free reviews until Fri Nov 07 2025 to showcase some of the refinements we've made. Comment |
* konflux | bumping task references. * konflux | build source image
- Update README.md - Build a source container (openshift-online#874) - update wif config to enable support for federated project (openshift-online#884) - pool usage after update (openshift-online#888) - Revert "pool usage after update (openshift-online#888)" (openshift-online#901) - Red Hat Konflux update ocm-cli (openshift-online#882) - update golang version (openshift-online#899) - chore(deps): update konflux references - added OWNERS file (openshift-online#937) - OCM-2093 | fix: misaligned list users result - OCM-2093 | fix: check eventual error raised by tabwriter's flush operation
- Update README.md - Build a source container (#874) - update wif config to enable support for federated project (#884) - pool usage after update (#888) - Revert "pool usage after update (#888)" (#901) - Red Hat Konflux update ocm-cli (#882) - update golang version (#899) - chore(deps): update konflux references - added OWNERS file (#937) - OCM-2093 | fix: misaligned list users result - OCM-2093 | fix: check eventual error raised by tabwriter's flush operation
1 participant
Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content
/ok-to-testFor more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization
Please follow the block sequence indentation style introduced by the proprosed PipelineRuns YAMLs, or keep using consistent indentation level through your customized PipelineRuns. When different levels are mixed, it will be changed to the proposed style.