知识卡片

普通读书笔记卡 · 1903.c.5.b

交付系统随系统生长

理解等级:高级

基础设施上线后还会不断打补丁、修复和改进,因此测试与部署自动化不应等临上线才建设。让实现早期就使用同一套变更交付系统,首次生产部署便是日常操作的一次延续,构建阶段也提前获得生产运行视角。把构建和运行视为连续生命周期,有助于减少首次上线的集中风险。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 基础设施代码测试策略 · 查看原书依据

      You should design and implement your change delivery system, including automated testing and deployment, along with the system itself. Use this system to support prerelease implementation, and continue using the same automation after the first release. Integrating build and run in this way massively de-risks

    参考来源

    - 位置:《Infrastructure As Code》第17章《基础设施代码测试策略》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch17.html) - 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“基础设施上线后还会不断打补丁、修复和改进,因此测试与部署自动化不应等临上线才建设”这一核心结论;正文的用途与边界据同小节后续论述整理。 - 原始内容:You should design and implement your change delivery system, including automated testing and deployment, along with the system itself. Use this system to support prerelease implementation, and continue using the same automation after the first release. Integrating build and run in this way massively de-risks