Skip to content

Red Hat Konflux purge configure-alertmanager-operator-pko - #614

Open
red-hat-konflux[bot] wants to merge 1 commit into
masterfrom
konflux-purge-configure-alertmanager-operator-pko
Open

Red Hat Konflux purge configure-alertmanager-operator-pko#614
red-hat-konflux[bot] wants to merge 1 commit into
masterfrom
konflux-purge-configure-alertmanager-operator-pko

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Pipelines as Code configuration removal

Summary by CodeRabbit

  • Chores
    • Removed automated pipeline configurations for pull-request and push-based builds.
    • Build triggers and associated pipeline execution settings are no longer included.

Signed-off-by: red-hat-konflux[bot] <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@openshift-ci
openshift-ci Bot requested review from Mhodesty and psav August 31, 2026 22:29
@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

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: d2c7b385-dabd-43de-8013-29a19b223262

📥 Commits

Reviewing files that changed from the base of the PR and between 9443642 and 9942a5e.

📒 Files selected for processing (2)
  • .tekton/configure-alertmanager-operator-pko-pull-request.yaml
  • .tekton/configure-alertmanager-operator-pko-push.yaml
💤 Files with no reviewable changes (2)
  • .tekton/configure-alertmanager-operator-pko-pull-request.yaml
  • .tekton/configure-alertmanager-operator-pko-push.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.


Walkthrough

Deletes the Tekton PipelineRun configurations for pull-request and push builds of the Alertmanager operator.

Changes

Cohort / File(s) Summary
Tekton PipelineRun removal
.tekton/configure-alertmanager-operator-pko-pull-request.yaml, .tekton/configure-alertmanager-operator-pko-push.yaml
Deletes the pull-request and push pipeline configurations, including triggers, build parameters, workspaces, service accounts, and Git-based pipeline references.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 9942a

This change removes the repository’s Pipelines as Code configuration for configure-alertmanager-operator-pko; no actionable merge-blocking risk remains beyond normal checks and 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 clearly identifies the Red Hat Konflux purge of the configure-alertmanager-operator-pko configuration, which matches the deleted PipelineRuns.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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 PASS. The pull request only deletes two .tekton PipelineRun YAML files. The diff contains 97 deletions and no additions, and it changes no Ginkgo test files or test titles. The Ginkgo declarations a…
Test Structure And Quality ✅ Passed PASS: The pull request only deletes two .tekton YAML PipelineRun files. The direct-parent diff contains 97 deletions and no Go test files, Ginkgo blocks, or test-related paths. The test-structure …
Microshift Test Compatibility ✅ Passed PASS: The pull request only deletes two .tekton PipelineRun configuration files. The committed diff contains 97 deletions and no added Ginkgo tests or MicroShift-incompatible API references. The cus…
Single Node Openshift (Sno) Test Compatibility ✅ Passed The pull request only deletes two .tekton PipelineRun YAML files. The parent-to-head diff contains no changed Go files and no added Ginkgo declarations. Therefore, the SNO compatibility check is not…
Topology-Aware Scheduling Compatibility ✅ Passed The check is not applicable. The pull request only deletes two .tekton PipelineRun configuration files. The committed diff contains no added or modified deployment manifests, operator code, or con…
Ote Binary Stdout Contract ✅ Passed PASS: The pull request changes only two deleted .tekton/*.yaml PipelineRun files. It introduces no main, init, Ginkgo setup, or other process-level code, and no stdout write. The repository cont…
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PASS: The pull request only deletes two Tekton PipelineRun YAML files. The parent-to-HEAD diff contains no new Ginkgo tests or changed test code, so the IPv4 and external-connectivity conditions do no…
No-Weak-Crypto ✅ Passed PASS: The pull request only deletes two .tekton PipelineRun YAML files. The diff contains no added code or configuration using MD5, SHA1, DES, 3DES, RC4, Blowfish, ECB, custom cryptography, or non-c…
Container-Privileges ✅ Passed PASS: The pull request only deletes two Tekton PipelineRun manifests. The parent versions contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root…
No-Sensitive-Data-In-Logs ✅ Passed PASS — The pull request only deletes two Tekton PipelineRun YAML files. The exact diff contains no logging statements, log configuration, or commands that print data. The deleted files contained only …
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

Full details: Stable And Deterministic Test Names

Explanation

PASS. The pull request only deletes two .tekton PipelineRun YAML files. The diff contains 97 deletions and no additions, and it changes no Ginkgo test files or test titles. The Ginkgo declarations are identical in HEAD^ and HEAD. Therefore, the pull request introduces no unstable or overly specific test name.

Full details: Test Structure And Quality

Explanation

PASS: The pull request only deletes two .tekton YAML PipelineRun files. The direct-parent diff contains 97 deletions and no Go test files, Ginkgo blocks, or test-related paths. The test-structure requirements therefore do not apply.

Full details: Microshift Test Compatibility

Explanation

PASS: The pull request only deletes two .tekton PipelineRun configuration files. The committed diff contains 97 deletions and no added Ginkgo tests or MicroShift-incompatible API references. The custom check is therefore not applicable.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

The pull request only deletes two .tekton PipelineRun YAML files. The parent-to-head diff contains no changed Go files and no added Ginkgo declarations. Therefore, the SNO compatibility check is not applicable.

Full details: Topology-Aware Scheduling Compatibility

Explanation

The check is not applicable. The pull request only deletes two .tekton PipelineRun configuration files. The committed diff contains no added or modified deployment manifests, operator code, or controllers, and introduces no scheduling constraints.

Full details: Ote Binary Stdout Contract

Explanation

PASS: The pull request changes only two deleted .tekton/*.yaml PipelineRun files. It introduces no main, init, Ginkgo setup, or other process-level code, and no stdout write. The repository contains a pre-existing fmt.Println in fips.go:init, but that file is unchanged, so it is not caused by this pull request.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS: The pull request only deletes two Tekton PipelineRun YAML files. The parent-to-HEAD diff contains no new Ginkgo tests or changed test code, so the IPv4 and external-connectivity conditions do not apply.

Full details: No-Weak-Crypto

Explanation

PASS: The pull request only deletes two .tekton PipelineRun YAML files. The diff contains no added code or configuration using MD5, SHA1, DES, 3DES, RC4, Blowfish, ECB, custom cryptography, or non-constant-time secret comparison. The only crypto-related match is deletion of an existing git-auth secret reference, so the pull request does not introduce a weak-crypto condition.

Full details: Container-Privileges

Explanation

PASS: The pull request only deletes two Tekton PipelineRun manifests. The parent versions contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root security settings. No privilege condition was introduced.

Full details: No-Sensitive-Data-In-Logs

Explanation

PASS — The pull request only deletes two Tekton PipelineRun YAML files. The exact diff contains no logging statements, log configuration, or commands that print data. The deleted files contained only build metadata, image parameters, and a templated git_auth_secret workspace reference; they did not expose secret values or log sensitive data. No logging behavior was introduced or changed.

✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux-purge-configure-alertmanager-operator-pko

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign xiaoyu74 for approval. For more information see the Code Review Process.

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

Details 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

@nephomaniac

Copy link
Copy Markdown
Contributor

Closing — these PaC configs belong to the new tenant (configure-alertmanager-operator-tenant on kflux-prd-rh03), not the old one. The old tenant's configs (camo-hcm-tenant) were already replaced by PR #591. Merging this would delete the active pipeline configs and break Konflux CI.

@nephomaniac

Copy link
Copy Markdown
Contributor

Do not merge — these PaC configs belong to the new tenant (configure-alertmanager-operator-tenant on kflux-prd-rh03), not the old one that was removed. The old tenant's configs (camo-hcm-tenant) were already replaced by PR #591. Merging this would delete the active Konflux pipeline configs and break CI. This PR should be closed.

@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

@red-hat-konflux[bot]: 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.

@codecov

codecov Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.61%. Comparing base (9443642) to head (9942a5e).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #614   +/-   ##
=======================================
  Coverage   67.61%   67.61%           
=======================================
  Files           8        8           
  Lines        1124     1124           
=======================================
  Hits          760      760           
  Misses        330      330           
  Partials       34       34           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant