Skip to content

Red Hat Konflux purge configure-alertmanager-operator-master - #615

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

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

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 pull-request and push automation configurations for the Alertmanager operator.
    • Eliminated associated triggers, build parameters, workspaces, credentials, and pipeline references.

Signed-off-by: red-hat-konflux[bot] <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@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 tnierman 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

@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: dfed1bde-4156-4de2-bbc8-9f41148c6f12

📥 Commits

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

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

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


Walkthrough

The change removes the pull-request and push PipelineRun configurations for the Alertmanager operator master branch.

Changes

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

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

Merge Risk: ⚪ Minimal · up to 88781

This change removes the repository’s Pipelines as Code configuration for the affected branch. 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-master configuration. This matches the removal of both PipelineRun configuration files.
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 commit only deletes two .tekton PipelineRun YAML files. It adds or changes no test files and introduces no Ginkgo test titles. The deleted files contained no It, Describe, Context, o…
Test Structure And Quality ✅ Passed PASS: The pull request changes only two .tekton PipelineRun YAML files, both deleted. The parent-to-HEAD diff contains no Ginkgo test source or test behavior changes. Therefore, this test-structure …
Microshift Test Compatibility ✅ Passed PASS: The pull request only deletes two .tekton PipelineRun YAML files. The commit adds no Ginkgo tests, test files, or test declarations. Existing Ginkgo tests are unchanged, so this check has no n…
Single Node Openshift (Sno) Test Compatibility ✅ Passed PASS: The pull request changes only two .tekton PipelineRun YAML files, and both changes are deletions. The parent-to-HEAD diff contains no added files, no Ginkgo declarations, and no new e2e tests.…
Topology-Aware Scheduling Compatibility ✅ Passed PASS: The commit only deletes two Tekton PipelineRun YAML files. The complete diff contains no added or modified deployment manifests, operator code, controllers, or scheduling constraints. The delete…
Ote Binary Stdout Contract ✅ Passed PASS. The PR only deletes two .tekton PipelineRun YAML files. It does not change Go entrypoints, OTE test setup, or logging code. The repository contains an existing fmt.Println in fips.go `in…
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PASS. The pull request only deletes two .tekton PipelineRun YAML files. The exact commit diff contains no added Ginkgo tests, test code, IPv4 assumptions, or external connectivity requirements. The …
No-Weak-Crypto ✅ Passed PASS: The pull request only deletes two Tekton YAML files. The parent-to-HEAD diff contains 0 additions and 117 deletions. No MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret-compari…
Container-Privileges ✅ Passed PASS: The pull request only deletes two Tekton PipelineRun YAML files. The parent-to-HEAD diff shows 117 deletions and no additions. The deleted manifests contain none of the checked conditions: `priv…
No-Sensitive-Data-In-Logs ✅ Passed PASS: The pull request only deletes two Tekton PipelineRun YAML files. The committed diff contains 117 deletions and no additions. Neither deleted file contains logging calls or log message content. T…
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 commit only deletes two .tekton PipelineRun YAML files. It adds or changes no test files and introduces no Ginkgo test titles. The deleted files contained no It, Describe, Context, or When calls.

Full details: Test Structure And Quality

Explanation

PASS: The pull request changes only two .tekton PipelineRun YAML files, both deleted. The parent-to-HEAD diff contains no Ginkgo test source or test behavior changes. Therefore, this test-structure check has no introduced condition to flag.

Full details: Microshift Test Compatibility

Explanation

PASS: The pull request only deletes two .tekton PipelineRun YAML files. The commit adds no Ginkgo tests, test files, or test declarations. Existing Ginkgo tests are unchanged, so this check has no newly introduced MicroShift compatibility issue.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

PASS: The pull request changes only two .tekton PipelineRun YAML files, and both changes are deletions. The parent-to-HEAD diff contains no added files, no Ginkgo declarations, and no new e2e tests. Therefore, the SNO multi-node compatibility check is not applicable.

Full details: Topology-Aware Scheduling Compatibility

Explanation

PASS: The commit only deletes two Tekton PipelineRun YAML files. The complete diff contains no added or modified deployment manifests, operator code, controllers, or scheduling constraints. The deleted files contained build parameters, workspaces, and pipeline references, not pod scheduling settings such as affinity, topology spread, node selectors, replicas, tolerations, or PDBs. Therefore, this topology-aware scheduling check is not applicable.

Full details: Ote Binary Stdout Contract

Explanation

PASS. The PR only deletes two .tekton PipelineRun YAML files. It does not change Go entrypoints, OTE test setup, or logging code. The repository contains an existing fmt.Println in fips.go init(), but the file is byte-for-byte unchanged from the parent revision. Therefore, the PR introduces no process-level stdout write and does not meet the failure condition.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS. The pull request only deletes two .tekton PipelineRun YAML files. The exact commit diff contains no added Ginkgo tests, test code, IPv4 assumptions, or external connectivity requirements. The check does not apply.

Full details: No-Weak-Crypto

Explanation

PASS: The pull request only deletes two Tekton YAML files. The parent-to-HEAD diff contains 0 additions and 117 deletions. No MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret-comparison code is introduced.

Full details: Container-Privileges

Explanation

PASS: The pull request only deletes two Tekton PipelineRun YAML files. The parent-to-HEAD diff shows 117 deletions and no additions. The deleted manifests contain none of the checked conditions: privileged: true, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation: true. The change introduces no container privilege configuration.

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

Explanation

PASS: The pull request only deletes two Tekton PipelineRun YAML files. The committed diff contains 117 deletions and no additions. Neither deleted file contains logging calls or log message content. The remaining repository search found no new sensitive-data logging pattern. Therefore, this pull request does not introduce logging that exposes passwords, tokens, API keys, PII, session IDs, internal hostnames, or customer data.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux-purge-configure-alertmanager-operator-master

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

@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 (8878146).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #615   +/-   ##
=======================================
  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