知识卡片
交付轴区分三种连续性
持续集成频繁合并并自动构建测试,持续交付保持可发布状态,持续部署进一步自动投产。三者关系紧密但不同,发布频率本身也不能证明系统质量;书中部分将交付等同频繁投产,需与自动部署的定义区分。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter 5. Knowing Thyself: The Cloud Native Maturity Matrix Tool · 查看原书依据
Continuous integration describes an organization that ensures new functionality is ready to be released at will—without needing to follow a strict release schedule (although a formal release schedule may still be followed). It often results in more frequent releases of new code to production.
参考来源
- 位置:《Cloud Native Transformation》第05章《Knowing Thyself: The Cloud Native Maturity Matrix Tool》(来源项目a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Transformation/_epub-src/OEBPS/ch05.xhtml)
- 结论依据:原文对本卡对象的定义、区别或前后条件给出直接解释,支持本卡的核心论点:持续集成频繁合并并自动构建测试,持续交付保持可发布状态,持续部署进一步自动投产。本卡进一步说明用途及适用边界;原文过强的保证另在正文限界。
- 原始内容:Continuous integration describes an organization that ensures new functionality is ready to be released at will—without needing to follow a strict release schedule (although a formal release schedule may still be followed). It often results in more frequent releases of new code to production.