Forgivesam168 AI Dev Workflow CI CD And Automation

CI/CD and Automation

Fast, reliable pipelines that catch defects early — not in production.

When to Use

• Designing a new CI/CD pipeline from scratch
• Adding quality gates to an existing pipeline
• Diagnosing slow or flaky pipelines
• Implementing Shift Left testing strategy
• Automating deployment workflows (staging, production promotion)

Core Principle: Shift Left

Move quality checks as early as possible — catch defects when they are cheapest to fix.

Rule: Every quality check that can run in CI should run in CI — not just in staging or production.

Pipeline Design

Recommended Stage Order

1. Fast Feedback (< 3 min)
   └── Lint + format check
   └── Unit tests (L1)
   └── Type check / build

2. Integration Gates (< 10 min)
   └── Integration tests (L2)
   └── Security scan (SAST)
   └── Dependency vulnerability check

3. Deployment Gate
   └── Staging deploy
   └── Smoke tests against staging
   └── Performance baseline check (if applicable)

4. Promotion (manual approval or auto, based on risk)
   └── Production deploy
   └── Post-deploy health check

Quality Gate Rules

Each stage is a hard gate — pipeline fails and stops if any check fails:

Performance Targets

Shift Left Implementation Checklist

• Pre-commit hooks: lint, format, secret detection (git-secrets, gitleaks)
• PR pipeline: unit tests, type check, build — must complete in < 3 min
• Security scanning integrated in PR pipeline (not just nightly)
• Dependency scanning on every PR (Dependabot, Snyk, pip-audit)
• Coverage gate enforced in CI (not just reported)
• Flaky tests identified and quarantined (not silently retried)

Anti-Patterns

Common Rationalizations

在設計和維護 CI/CD 管道時，AI 可能以下列藉口降低品質閘門標準：

Verification

在 CI/CD 配置完成或修改後，逐項確認：

• Test-Path .github/workflows/*.yml 或 Test-Path .gitlab-ci.yml 至少一項回傳 True（pipeline 配置檔存在）
• 每個 PR 觸發 unit test + lint + build（不只是 push to main）
• Coverage gate 已設定且閾值 ≥80%（或符合專案標準）
• Security / dependency scan 已整合於 PR pipeline（非僅 nightly）
• 所有 stage 均為 hard gate（失敗即停止，不得 continue-on-error: true）
• Pipeline 總時長 < 15 分鐘（Fast Feedback stage < 3 分鐘）
• Flaky 測試隔離機制存在（quarantine tag 或分離 job）

Source: forgivesam168/ai-dev-workflow — distributed by TomeVault.