Your Name
b5adf77a9f
CD Pipeline / tests (push) Failing after 1m27s
CD Pipeline / build-and-deploy (push) Has been skipped
CD Pipeline / post-deploy-checks (push) Has been skipped
Code Review / ai-code-review (push) Successful in 48s
fix(ci): make Telegram notifications non-blocking on CD pipeline
統帥鐵證：tests/build-and-deploy 步驟內 'Notify Pipeline Start/Failure'
curl 400 → 整個 job exit 22 → 從 5/1 起連續 14 個 commit 部署被擋。
根本問題：通知步驟是觀察用，不該成為 CI 主流程的 hard requirement。
curl -fS 預設 fail-on-HTTP-error，配上 Telegram bot 任何短暫故障
（token revoke、bot 被踢出 chat、API rate limit）就把整條 pipeline 擊垮。
修法：對齊 line 922 既有正確 pattern，5 處 curl 全部加
`|| echo "TG notify failed (non-fatal): exit=$?"`
涉及 step:
- Notify Pipeline Start (line 79)
- Notify Pipeline Failure × tests (line 236)
- Notify Pipeline Failure × build-and-deploy (line 779)
- Notify Pipeline Failure × post-deploy-checks (line 938)
- (line 924 已是正確 pattern, 不動)
副效應：notification 失敗從此只會在 log 留 warning，不擋 CI。
真正的 telegram 故障由系統其他監控機制（alertmanager_health 等）負責。
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-03 00:00:20 +08:00
..
2026-04-11 02:47:10 +08:00
2026-04-30 15:05:16 +08:00
2026-05-03 00:00:20 +08:00
2026-05-01 20:59:14 +08:00
2026-04-30 15:05:16 +08:00
2026-04-30 15:05:16 +08:00
2026-05-01 13:30:32 +08:00
2026-04-06 12:17:36 +08:00