此卡片不在当前主题的阅读序列中,可返回主题继续阅读。
知识卡片
持续交付逐次构建质量
持续交付把大批发布拆成频繁的小变更,每次都验证到可发布程度。问题更早暴露且易定位,也能早获用户反馈;常规变更与紧急修复共用熟练流程,治理检查可嵌入自动化。优势来自持续完成质量工作,而不是单纯提高发布次数。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 核心基础设施交付工作流 · 查看原书依据
Testing each change thoroughly enough to release, one by one, means issues are discovered and fixed sooner, when it’s simpler and cheaper to do so. A common failing of longer release cycles is that there is not enough time to fix everything discovered at the end, leading to kludgy workarounds and accepting “known issues.” CD
参考来源
- 位置:《Infrastructure As Code》第14章《核心基础设施交付工作流》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch14.html)
- 结论依据:原文说明持续交付把大批发布拆成频繁的小变更,每次都验证到可发布程度;本卡据此解释其用途及适用边界。
- 原始内容:Testing each change thoroughly enough to release, one by one, means issues are discovered and fixed sooner, when it’s simpler and cheaper to do so. A common failing of longer release cycles is that there is not enough time to fix everything discovered at the end, leading to kludgy workarounds and accepting “known issues.” CD