持续交付和持续部署之间的区别是什么？

Question

持续交付和持续部署之间的区别是什么？

Accepted Answer

**持续交付**和**持续部署**都自动化了发布流程，并共享缩写 CD，但它们在一个关键方面有所不同：**持续交付**使代码准备好通过**手动**发布触发器进行部署，而**持续部署**会**自动**发布，没有手动步骤。

## Continuous Delivery — 自动化、手动触发

```text
CONTINUOUS DELIVERY: every change that passes the pipeline is ready to deploy, but
the actual production release is triggered MANUALLY (a human decision):
  Code → build → test → (auto-deploy to staging) → [MANUAL approval] → deploy to prod
  → code is ALWAYS in a deployable state; releasing is "one click" when you choose
  → keeps a human gate before production (approval, timing control)
```

## Continuous Deployment — 完全自动化

```text
CONTINUOUS DEPLOYMENT: every change that passes ALL pipeline stages is AUTOMATICALLY
deployed to production — NO manual step:
  Code → build → test → deploy to prod (automatically, if all checks pass)
  → the pipeline IS the only gate; passing tests = deployed
  → requires HIGH confidence in automated testing (no human safety check)
```

## 关键区别

```text
BOTH automate the pipeline; the difference is the FINAL production step:
  DELIVERY    → ready to deploy; a HUMAN decides when to release (manual trigger)
  DEPLOYMENT  → AUTOMATICALLY released on passing the pipeline (no human step)
→ Deployment goes one step further (fully automatic). Delivery keeps a manual gate.
```

## 在它们之间选择

```text
CONTINUOUS DELIVERY → when you want control over release timing, manual approval,
  or testing/confidence isn't yet sufficient for fully-automatic prod releases
CONTINUOUS DEPLOYMENT → when you have strong automated tests and want maximum speed
  (every change live quickly) — requires mature testing and monitoring
```

## 为什么这很重要

理解持续交付和持续部署之间的区别是有价值的，因为它们经常被混淆（共享