知识卡片
限制未集成变更的存活时间
实现层的持续集成需要可复现的合并、构建步骤,自动化测试,以及对未集成变更存活时间的上限。合并频率应随变化速度调整:在其他人基于旧模型做出大量不兼容工作之前合并。原书提到多数敏捷项目至少每日合并,这是描述当时做法,不是所有团队的固定频率。
短周期反馈降低因担心破坏现有功能而复制一套实现的诱因,也便于尽早发现模型分叉。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第14章|Continuous Integration · 查看原书依据
Most Agile projects have at least daily merges of each developer's code changes. The frequency can be adjusted to the pace of change, as long as any unintegrated change would be merged before a significant amount of incompatible work could be done by other team members.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第102章《Continuous Integration》(源文件:_epub-src/0321125215_ch14lev1sec2.html;单元01)
- 结论依据:原文列出有效集成过程的三项共同特征,并以变化速度与他人不兼容工作量限定频率。
- 原始内容:Most Agile projects have at least daily merges of each developer's code changes. The frequency can be adjusted to the pace of change, as long as any unintegrated change would be merged before a significant amount of incompatible work could be done by other team members.