知识卡片
持续集成未完工作
持续集成要求把所有在制工作频繁合并并测试,而不是等各分支“完成”后才集成。持续交付进一步要求合并后的代码保持可投入生产。早期暴露组合问题能把质量建立在开发过程里;只对各自完成的孤立分支做测试,仍可能留下集成风险。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 什么是基础设施即代码 · 查看原书依据
Effective infrastructure teams are rigorous about testing. They use automation to deploy and test each component of their system and integrate all the work everyone has in progress. They test as they work rather than waiting until they’ve finished. The idea is to build quality in rather than trying to test quality in. One part
参考来源
- 位置:《Infrastructure As Code》第1章《什么是基础设施即代码》(来源项目 book-sources,源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch01.html)
- 结论依据:原文对该概念的定义、应用条件与作用机制直接支持上述解释。
- 原始内容:Effective infrastructure teams are rigorous about testing. They use automation to deploy and test each component of their system and integrate all the work everyone has in progress. They test as they work rather than waiting until they’ve finished. The idea is to build quality in rather than trying to test quality in. One part