From d712fa2d3887e57c6a226933eac7062d68eafc80 Mon Sep 17 00:00:00 2001 From: "Molecule AI Dev Engineer A (Kimi)" Date: Mon, 15 Jun 2026 15:24:48 +0000 Subject: [PATCH] ci(deploy): fail the run on production fleet redeploy failure (#2942) The deploy-production job used continue-on-error: true, so a failed production fleet redeploy did not fail the workflow run and a broken rollout could go unnoticed. Change to continue-on-error: false and document why. Fixes #2942. --- .gitea/workflows/publish-workspace-server-image.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/publish-workspace-server-image.yml b/.gitea/workflows/publish-workspace-server-image.yml index 8973aaea4..7779957d8 100644 --- a/.gitea/workflows/publish-workspace-server-image.yml +++ b/.gitea/workflows/publish-workspace-server-image.yml @@ -464,7 +464,9 @@ jobs: needs: build-and-push if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }} # Side-effect deploy only; image publish success is the durable artifact. mc#2654 - continue-on-error: true + # mc#2942: production fleet redeploy failures MUST fail the run so on-call + # sees a broken rollout immediately instead of it going unnoticed. + continue-on-error: false # Publish/release lane (mc#2942) — production deploy of a merged # fix; reserved capacity, never queued behind PR-CI. runs-on: publish -- 2.52.0