ci: remove gitea-merge-queue schedule: (queue absorbed into operator conductor) #11

2026-06-10T10:13:50Z

devops-engineer commented

2026-06-10 10:13:50 +00:00

Remove the `schedule:` trigger from gitea-merge-queue.yml (execution absorbed into the operator conductor)

Measurement (Gitea DB action_run_job, 7d, posted on operator-config#157): the scheduled queue job is the top remaining CI meta-job after event-driven dispatch (operator-config#157/#159): 312 jobs/hr around the clock across 26 repos (288/day in this repo alone) = ~52.4k container jobs/week, ~58–65 in-job hours/week plus a full container lifecycle per tick — and ~99% of ticks are no-ops ("merge queue empty" / fail-closed holds; verified in this fleet's action logs).

What replaced it: since operator-config#194 (merged + autoheal-applied), the operator conductor tick (molecule-core-cron-bot.sh conductor, every 5 min — same cadence as this schedule) runs this repo's merge-queue in-process, with this repo's own workflow env and this repo's own script version (parsed/fetched per tick, sha256-pinned before execution). Live parity was proven before this PR was opened: the conductor pass reproduces this repo's scheduled-run behavior exactly.

This PR changes no policy: the queue contract, merge bar, labels, and workflow_dispatch (manual run) are untouched. Only the schedule: block is removed so the 5-min container polling stops.

Kill-switch / rollback:

Conductor-side: touch /etc/molecule-bootstrap/molecule-ci-conductor-fleet.disabled (operator host) — disables the in-process pass.
Repo-side: revert this PR (re-adds schedule: - cron: "*/5 * * * *"); workflow_dispatch works at any time.

Projected saving for this repo: ~2,016 scheduler jobs/week.

🤖 Generated with Claude Code

SOP checklist

Comprehensive testing performed — change is a workflow-trigger removal (no code/logic). Verified: (a) transformed YAML parses and workflow_dispatch retained, validated programmatically for all 26 repos before opening; (b) the replacement (conductor fleet pass, operator-config#194) proven live: dry + real runs reproduce this repo's scheduled-job behavior byte-for-byte (same script version, same env, same fail-closed outcomes), full installed-path conductor tick green (status-reaper rc=0, merge-queue rc=0, merge-queue-fleet rc=0, journal 2026-06-10T10:12:58Z).
Local-postgres E2E run — N/A: CI workflow trigger change only, no application/database code.
Staging-smoke verified or pending — the conductor fleet pass is already live on the operator host (autoheal-applied 2026-06-10T09:40Z) and has been observed processing this repo class in production while the schedule still runs in parallel; removing schedule: only stops the redundant container polling.
Root-cause not symptom — root cause: schedule-based polling burns a full CI container lifecycle every 5 min per repo (~52k jobs/week fleet-wide, ~99% no-ops) for work an existing operator-side tick can do in-process; this PR removes the polling vehicle, not the queue policy.
Five-Axis review walked — correctness: YAML validated + behavior parity proven; readability: in-file note documents the absorption + rollback; architecture: execution moved to the conductor (operator-config#158 pattern), policy untouched; security: workflow loses its schedule-time token use, conductor side sha256-pins script bytes; performance: removes ~2,016 scheduler jobs/week for this repo.
No backwards-compat shim / dead code added — yes, none: the schedule: block is deleted (not commented-as-fallback); workflow_dispatch is retained as the designed manual vehicle, not a shim.
Memory/saved-feedback consulted — gate semantics are CTO-governed (absorb execution, never policy); kill-switch + rollback in every change; verify the real artifact (live conductor tick observed, not assumed); parallel-work check done (no competing PRs touch this file).

## Remove the `schedule:` trigger from gitea-merge-queue.yml (execution absorbed into the operator conductor) **Measurement (Gitea DB `action_run_job`, 7d, posted on operator-config#157):** the scheduled `queue` job is the top remaining CI meta-job after event-driven dispatch (operator-config#157/#159): **312 jobs/hr around the clock across 26 repos** (288/day in this repo alone) = ~52.4k container jobs/week, ~58–65 in-job hours/week plus a full container lifecycle per tick — and ~99% of ticks are no-ops ("merge queue empty" / fail-closed holds; verified in this fleet's action logs). **What replaced it:** since operator-config#194 (merged + autoheal-applied), the operator conductor tick (`molecule-core-cron-bot.sh conductor`, every 5 min — same cadence as this schedule) runs this repo's merge-queue **in-process**, with **this repo's own workflow env and this repo's own script version** (parsed/fetched per tick, sha256-pinned before execution). Live parity was proven before this PR was opened: the conductor pass reproduces this repo's scheduled-run behavior exactly. **This PR changes no policy:** the queue contract, merge bar, labels, and `workflow_dispatch` (manual run) are untouched. Only the `schedule:` block is removed so the 5-min container polling stops. **Kill-switch / rollback:** 1. Conductor-side: `touch /etc/molecule-bootstrap/molecule-ci-conductor-fleet.disabled` (operator host) — disables the in-process pass. 2. Repo-side: revert this PR (re-adds `schedule: - cron: "*/5 * * * *"`); `workflow_dispatch` works at any time. Projected saving for this repo: ~2,016 scheduler jobs/week. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- ## SOP checklist 1. **Comprehensive testing performed** — change is a workflow-trigger removal (no code/logic). Verified: (a) transformed YAML parses and `workflow_dispatch` retained, validated programmatically for all 26 repos before opening; (b) the replacement (conductor fleet pass, operator-config#194) proven live: dry + real runs reproduce this repo's scheduled-job behavior byte-for-byte (same script version, same env, same fail-closed outcomes), full installed-path conductor tick green (status-reaper rc=0, merge-queue rc=0, merge-queue-fleet rc=0, journal 2026-06-10T10:12:58Z). 2. **Local-postgres E2E run** — N/A: CI workflow trigger change only, no application/database code. 3. **Staging-smoke verified or pending** — the conductor fleet pass is already live on the operator host (autoheal-applied 2026-06-10T09:40Z) and has been observed processing this repo class in production while the schedule still runs in parallel; removing `schedule:` only stops the redundant container polling. 4. **Root-cause not symptom** — root cause: schedule-based polling burns a full CI container lifecycle every 5 min per repo (~52k jobs/week fleet-wide, ~99% no-ops) for work an existing operator-side tick can do in-process; this PR removes the polling vehicle, not the queue policy. 5. **Five-Axis review walked** — correctness: YAML validated + behavior parity proven; readability: in-file note documents the absorption + rollback; architecture: execution moved to the conductor (operator-config#158 pattern), policy untouched; security: workflow loses its schedule-time token use, conductor side sha256-pins script bytes; performance: removes ~2,016 scheduler jobs/week for this repo. 6. **No backwards-compat shim / dead code added** — yes, none: the `schedule:` block is deleted (not commented-as-fallback); `workflow_dispatch` is retained as the designed manual vehicle, not a shim. 7. **Memory/saved-feedback consulted** — gate semantics are CTO-governed (absorb execution, never policy); kill-switch + rollback in every change; verify the real artifact (live conductor tick observed, not assumed); parallel-work check done (no competing PRs touch this file).

devops-engineer added 1 commit 2026-06-10 10:13:50 +00:00

ci: remove gitea-merge-queue schedule (absorbed into operator conductor, operator-config#194)

CI / validate (pull_request) Successful in 22s

Details

CI / validate (push) Successful in 1m49s

Details

sop-checklist-gate / gate (pull_request_target) Failing after 7s

Details

046ab5abad

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

devops-engineer requested review from agent-reviewer 2026-06-10 10:13:54 +00:00

devops-engineer requested review from agent-reviewer-cr2 2026-06-10 10:13:55 +00:00

devops-engineer requested review from agent-researcher 2026-06-10 10:13:56 +00:00

core-qa approved these changes 2026-06-10 16:15:24 +00:00

core-qa left a comment

verified: schedule-removal (gitea-merge-queue schedule absorbed into operator conductor), required CI green

core-security approved these changes 2026-06-10 16:15:28 +00:00

core-security left a comment

verified: schedule-removal (gitea-merge-queue schedule absorbed into operator conductor), required CI green

devops-engineer merged commit 4df7e4c58c into main

2026-06-10 16:15:34 +00:00

Sign in to join this conversation.

No Reviewers

agent-reviewer

agent-reviewer-cr2

agent-researcher

core-qa

core-security

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-ai-plugin-ecc#11

ci: remove gitea-merge-queue schedule: (queue absorbed into operator conductor) #11

Remove the schedule: trigger from gitea-merge-queue.yml (execution absorbed into the operator conductor)

SOP checklist

ci: remove gitea-merge-queue `schedule:` (queue absorbed into operator conductor) #11

Remove the `schedule:` trigger from gitea-merge-queue.yml (execution absorbed into the operator conductor)