[ci-hardening] Triage the ~34 continue-on-error masks before mc#1982 due (2026-06-11) #2113

Closed
opened 2026-06-02 00:27:34 +00:00 by devops-engineer · 0 comments
Member

mc#774 aged out and was renewed to mc#1982 via #2112 (clean rename, no triage). The 14-day cap exists to FORCE a real review, which the rename deferred. Before 2026-06-11:

  • Audit each continue-on-error: true job-level mask across the 34 workflows.
  • For each: has the underlying defect been fixed / has the lane been clean for N main runs? If yes → flip to continue-on-error: false and remove the mask.
  • Only the genuinely-still-needed masks should carry forward to the next renewal.
  • Pay special attention to destructive/janitor + publish/deploy workflows.

Refs mc#774, mc#1982, #2112. Owner: CI hardening. Do NOT just rename to mc#2xxx next cycle — that is the kick-the-can the cap is meant to prevent.

mc#774 aged out and was renewed to mc#1982 via #2112 (clean rename, no triage). The 14-day cap exists to FORCE a real review, which the rename deferred. Before 2026-06-11: - Audit each `continue-on-error: true` job-level mask across the 34 workflows. - For each: has the underlying defect been fixed / has the lane been clean for N main runs? If yes → flip to `continue-on-error: false` and remove the mask. - Only the genuinely-still-needed masks should carry forward to the next renewal. - Pay special attention to destructive/janitor + publish/deploy workflows. Refs mc#774, mc#1982, #2112. Owner: CI hardening. Do NOT just rename to mc#2xxx next cycle — that is the kick-the-can the cap is meant to prevent.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2113