知识卡片
扇入交付的边界
扇入先独立构建和测试组件,再把选定组合一起集成测试并向后晋级。后续阶段仅部署已改变的栈,可并行时并行,因此兼顾独立变更与组合可靠性。但组件和团队过多时协调成本迅速上升,宜用于同一流对齐团队拥有的一组组件。
结构图:
flowchart TD
A[独立组件构建测试] --> C[组合部署与集成验证]
B[其他组件构建测试] --> C
C --> D[组合版本一起晋级]
D --> E[仅部署改变的组件]
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建与分发基础设施代码 · 查看原书依据
A fan-in integration workflow builds and tests each deployable component separately, to ensure it is independently deployable and to check that it works correctly.4 Figure 15-9 shows a fan-in workflow for the menu service infrastructure stacks. Figure 15-9. Fan-in delivery workflow When any one of
参考来源
- 位置:《Infrastructure As Code》第15章《构建与分发基础设施代码》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch15.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“扇入先独立构建和测试组件,再把选定组合一起集成测试并向后晋级”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:A fan-in integration workflow builds and tests each deployable component separately, to ensure it is independently deployable and to check that it works correctly.4 Figure 15-9 shows a fan-in workflow for the menu service infrastructure stacks. Figure 15-9. Fan-in delivery workflow When any one of