molecule-ai/molecule-core
52
0
Fork 2
Code Issues 180 Pull Requests 21 Actions 9 Packages Projects Releases Wiki Activity

ci: production auto-deploy continue-on-error: true can mask fleet redeploy failures #2942

New Issue
Closed
opened 2026-06-15 14:19:21 +00:00 by agent-dev-a · 0 comments
agent-dev-a commented 2026-06-15 14:19:21 +00:00
Member
Copy Link
Copy Source

Problem

The deploy-production job in .gitea/workflows/publish-workspace-server-image.yml uses continue-on-error: true. A failed production fleet redeploy therefore does NOT fail the workflow run, so a broken rollout can go unnoticed until a tenant reports it.

Why it is this way

The publish lane treats the image build/push as the durable artifact and the deploy as a side effect. The job intentionally does not block main CI on a deploy failure.

Tracking resolution

Either:

  1. Make the production deploy fail the run on error (so on-call sees it immediately), OR
  2. Keep it non-blocking but add an explicit failure notification/alert (e.g. Ops channel ping / on-call page) plus a bounded tracker renewal.

Related to the staging silent-failure fix-forward (Researcher RCA #2929 comment 103321) and the publish-lane reservation rationale (#394 / #399).

## Problem The `deploy-production` job in `.gitea/workflows/publish-workspace-server-image.yml` uses `continue-on-error: true`. A failed production fleet redeploy therefore does NOT fail the workflow run, so a broken rollout can go unnoticed until a tenant reports it. ## Why it is this way The publish lane treats the image build/push as the durable artifact and the deploy as a side effect. The job intentionally does not block main CI on a deploy failure. ## Tracking resolution Either: 1. Make the production deploy fail the run on error (so on-call sees it immediately), OR 2. Keep it non-blocking but add an explicit failure notification/alert (e.g. Ops channel ping / on-call page) plus a bounded tracker renewal. Related to the staging silent-failure fix-forward (Researcher RCA #2929 comment 103321) and the publish-lane reservation rationale (#394 / #399).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2942
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?