Skip to content

Remove fullsend Jira poll integration - #1062

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
samanthajayasinghe:remove-fullsend-jira
Nov 17, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
samanthajayasinghe:remove-fullsend-jira

Conversation

@samanthajayasinghe

@samanthajayasinghe samanthajayasinghe commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Remove .github/workflows/fullsend-poll-jira.yml, the scheduled workflow that polled Jira (project ROSAENG, component osdctl, non-Closed/Done) every 5 minutes and handed resulting dispatches to the fullsend harness for agent execution
  • This fully disables the Jira integration: no more Jira polling, and the JIRA_TOKEN / JIRA_USER_EMAIL secrets and JIRA_BASE_URL var are no longer consumed by any workflow
  • The GitHub-event-based fullsend shim (.github/workflows/fullsend.yaml) is unchanged and unaffected

Notes

  • .fullsend/harness/*.yaml and .fullsend/policies/triage.yaml contain Jira-path env overrides and sandbox egress rules, but they only activate on work_item dispatches that the removed poll workflow produced — they are inert without it and are left untouched to avoid disturbing the general fullsend per-repo setup

Test plan

  • CI passes
  • No remaining workflow references Jira secrets/vars

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Jira polling automation is no longer available, including scheduled polling and manual triggering. This change affects background workflow behavior; it does not add or change any end-user-facing application features.

Drops the scheduled workflow that polled Jira (ROSAENG, component osdctl)
every 5 minutes and dispatched issues/comments to the fullsend harness.
The GitHub-event-based fullsend shim is unaffected.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

No actionable comments were generated in the recent review.

Walkthrough

The pull request deletes the GitHub Actions workflow that polled Jira and passed routed events to a reusable fullsend harness workflow.

Changes

Jira polling workflow

Layer / File(s) Summary
Remove Jira polling workflow
.github/workflows/fullsend-poll-jira.yml
The workflow’s scheduled and manual triggers, Jira polling configuration, dispatch-matrix construction, and reusable harness invocation were removed.

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Suggested reviewers: geowa4

Merge Risk: Minimal · up to 2f91c

This change removes the scheduled Jira polling workflow, so the Jira-triggered fullsend runs stop. The GitHub-event-based path is unchanged. No merge-blocking risk is identified, and the change can be reverted by restoring the file.

Pre-merge checks: Passed 14

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title "Remove fullsend Jira poll integration" matches the main change. The PR deletes the workflow .github/workflows/fullsend-poll-jira.yml, which polled Jira for osdctl issues and dispatched them…
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 The check applies to Ginkgo test titles (It, Describe, Context, When, and similar). The reviewed range changes one file: .github/workflows/fullsend-poll-jira.yml, deleted (D). The diff adds no test …
Test Structure And Quality Passed The check applies to Ginkgo test code. This PR changes only one file: .github/workflows/fullsend-poll-jira.yml is deleted (D in the name-status output). The diff adds no lines matching It(, `g.I…
Microshift Test Compatibility Passed The check applies only when new Ginkgo e2e tests (It, Describe, Context, When) are added. The pull request changes one file: .github/workflows/fullsend-poll-jira.yml is deleted (0 insertions, 114 de…
Single Node Openshift (Sno) Test Compatibility Passed The check applies only when new Ginkgo e2e tests (It, Describe, Context, When, and similar) are added. The pull request changes one file: it deletes .github/workflows/fullsend-poll-jira.yml (status …
Topology-Aware Scheduling Compatibility Passed The check applies only when deployment manifests, operator code, or controllers are added or modified. This PR changes one file: it deletes .github/workflows/fullsend-poll-jira.yml (114 lines, GitHu…
Ote Binary Stdout Contract Passed The check is inapplicable. The reviewed range changes exactly one file: the deletion of .github/workflows/fullsend-poll-jira.yml (status D, per git diff --name-status against the review base). Tha…
Ipv6 And Disconnected Network Test Compatibility Passed The check applies only when new Ginkgo e2e tests are added. The PR's complete diff is one file deletion: D .github/workflows/fullsend-poll-jira.yml. A search of added lines for It/Describe/Context/W…
No-Weak-Crypto Passed The no-weak-crypto check flags use of MD5, SHA1, DES, RC4, 3DES, Blowfish, or ECB mode, custom crypto implementations, and non-constant-time comparison of secrets or tokens. The pull request changes o…
Container-Privileges Passed The check is for privileged container settings in container/Kubernetes manifests. The PR's only file change is the deletion of .github/workflows/fullsend-poll-jira.yml (status D). The diff adds no l…
No-Sensitive-Data-In-Logs Passed The pull request changes one file: .github/workflows/fullsend-poll-jira.yml is deleted (D). The diff has no added lines, so it adds no new logging statements, log output, or other code that could …
Full details: Title check

Explanation

The title "Remove fullsend Jira poll integration" matches the main change. The PR deletes the workflow .github/workflows/fullsend-poll-jira.yml, which polled Jira for osdctl issues and dispatched them to the fullsend harness. The title names the removed component and the action taken. It is specific and concise, and it does not describe anything absent from the changeset.

Full details: Stable And Deterministic Test Names

Explanation

The check applies to Ginkgo test titles (It, Describe, Context, When, and similar). The reviewed range changes one file: .github/workflows/fullsend-poll-jira.yml, deleted (D). The diff adds no test titles. A search of *_test.go changes found no added It/Describe/Context/When calls. No test title in this PR contains a dynamic value, legacy openshift-tests-private prefix, or Polarion ID. The check is inapplicable to this PR, so it passes.

Full details: Test Structure And Quality

Explanation

The check applies to Ginkgo test code. This PR changes only one file: .github/workflows/fullsend-poll-jira.yml is deleted (D in the name-status output). The diff adds no lines matching It(, g.It(, Describe(, Context(, Eventually, Consistently, or ginkgo. No Ginkgo test is added, modified, or removed, so none of the six quality requirements (single responsibility, setup/cleanup, timeouts, assertion messages, codebase consistency, informing for new tests) applies. The check is inapplicable and passes.

Full details: Microshift Test Compatibility

Explanation

The check applies only when new Ginkgo e2e tests (It, Describe, Context, When) are added. The pull request changes one file: .github/workflows/fullsend-poll-jira.yml is deleted (0 insertions, 114 deletions). The diff contains no added Ginkgo blocks or test code, so no new test needs a MicroShift compatibility review. The check is inapplicable and passes.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

The check applies only when new Ginkgo e2e tests (It, Describe, Context, When, and similar) are added. The pull request changes one file: it deletes .github/workflows/fullsend-poll-jira.yml (status D, the only entry in the name-status inventory). A search of the patch for added It(), Describe(), Context(), When(), and g.-prefixed forms returned no matches. No new Ginkgo tests are introduced, so there is no multi-node or HA assumption to evaluate. The check is inapplicable and passes.

Full details: Topology-Aware Scheduling Compatibility

Explanation

The check applies only when deployment manifests, operator code, or controllers are added or modified. This PR changes one file: it deletes .github/workflows/fullsend-poll-jira.yml (114 lines, GitHub Actions workflow). The changed-file inventory from git diff --name-status shows only D .github/workflows/fullsend-poll-jira.yml. The deleted file is a scheduled CI workflow that polls Jira and calls a reusable harness workflow. It is not a deployment manifest, operator, or controller. It also adds no scheduling constraints such as anti-affinity, topology spread, replica counts, nodeSelectors, tolerations, or PDBs. No flagged pattern is introduced, so the check is inapplicable and passes.

Full details: Ote Binary Stdout Contract

Explanation

The check is inapplicable. The reviewed range changes exactly one file: the deletion of .github/workflows/fullsend-poll-jira.yml (status D, per git diff --name-status against the review base). That file is a GitHub Actions workflow, not an OpenShift Tests Extension binary or Go process-level code. The PR adds or modifies no main(), init(), TestMain(), suite setup, klog, or log configuration, so no process-level stdout write is introduced or changed. The check's failure conditions cannot be triggered by this change.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

The check applies only when new Ginkgo e2e tests are added. The PR's complete diff is one file deletion: D .github/workflows/fullsend-poll-jira.yml. A search of added lines for It/Describe/Context/When/DescribeTable/Entry calls returned no matches. No new e2e tests were added, and no IPv4 assumptions or external connectivity were introduced by this change. The check is inapplicable, so it passes.

Full details: No-Weak-Crypto

Explanation

The no-weak-crypto check flags use of MD5, SHA1, DES, RC4, 3DES, Blowfish, or ECB mode, custom crypto implementations, and non-constant-time comparison of secrets or tokens. The pull request changes one file: git diff --name-status shows D .github/workflows/fullsend-poll-jira.yml, a deletion of a 114-line GitHub Actions workflow. The added-line set is empty, so the diff adds no cryptographic code. A scan of the added lines for weak algorithm names, HMAC, comparison operators, and "crypto" found no matches. The removed workflow passed Jira secrets to a pinned harness. Removing it does not add a weak primitive or a non-constant-time comparison. No explicit failure condition is triggered.

Full details: Container-Privileges

Explanation

The check is for privileged container settings in container/Kubernetes manifests. The PR's only file change is the deletion of .github/workflows/fullsend-poll-jira.yml (status D). The diff adds no lines. A grep of added lines for privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, runAsUser, root, allowPrivilegeEscalation, and securityContext found no matches. The PR introduces no privileged container configuration, so the check passes.

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

Explanation

The pull request changes one file: .github/workflows/fullsend-poll-jira.yml is deleted (D). The diff has no added lines, so it adds no new logging statements, log output, or other code that could expose passwords, tokens, API keys, PII, session IDs, internal hostnames, or customer data. Removing the workflow removes its existing behavior, and the check does not treat that removal as a logging exposure. The .fullsend/ harness and policy files are not in the diff and stay unchanged. The check does not apply to a deletion-only change that adds no logging, so the result is PASS.

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML; Path: .coderabbit.yaml
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: e3b4b70f-d34c-42f1-830e-96fd46878d3c
Commits

Reviewing files that changed from the base of the PR and between 0c15ef4 and 2f91c47.

Files selected for processing: 1

  • .github/workflows/fullsend-poll-jira.yml
Files with no reviewable changes: 1

  • .github/workflows/fullsend-poll-jira.yml

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

@xiaoyu74

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 16, 2026
@openshift-ci

openshift-ci Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xiaoyu74

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:

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 16, 2026
@openshift-ci

openshift-ci Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

@samanthajayasinghe: 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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 3052747 into openshift:master Nov 17, 2026
37 checks passed
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants