infra/.woodpecker
Viktor Barzin 88c86e2109
All checks were successful
ci/woodpecker/push/default Pipeline was successful
ci: Slack-notify failed pipeline runs only
Viktor doesn't want a Slack message for every CI run — only failures.
The infra apply pipeline posted a status line to #general on every push,
and the renew-tls / postmortem-todos / registry-config-sync /
pve-nfs-exports-sync crons posted on every scheduled run (~30+ routine
messages a week). Now: the apply pipeline's success post is gone
(notify-failure already covers failures), all cron notifies are
status:[failure] with explicit FAILED texts, and drift-detection is
silent when all stacks are clean (still posts drift findings and errors,
and gains a hard-failure catch step it previously lacked). Kept:
notify-nonadmin-push (org audit feed) and the actionable provision-user
post. Per-app deploy template in ci-cd.md updated to match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 07:27:43 +00:00
..
breakglass-infra-ci.yml ci: retire in-cluster infra-ci build; breakglass becomes manual ghcr pull-and-save (ADR-0002 #30) 2026-06-13 10:07:58 +00:00
default.yml ci: Slack-notify failed pipeline runs only 2026-07-02 07:27:43 +00:00
drift-detection.yml ci: Slack-notify failed pipeline runs only 2026-07-02 07:27:43 +00:00
issue-automation.yml woodpecker: disable partial clone (partial: false) — fix intermittent git exit-128 2026-06-19 09:06:44 +00:00
postmortem-todos.yml ci: Slack-notify failed pipeline runs only 2026-07-02 07:27:43 +00:00
provision-user.yml woodpecker: disable partial clone (partial: false) — fix intermittent git exit-128 2026-06-19 09:06:44 +00:00
pve-nfs-exports-sync.yml ci: Slack-notify failed pipeline runs only 2026-07-02 07:27:43 +00:00
registry-config-sync.yml ci: Slack-notify failed pipeline runs only 2026-07-02 07:27:43 +00:00
renew-tls.yml ci: Slack-notify failed pipeline runs only 2026-07-02 07:27:43 +00:00