知识卡片

普通读书笔记卡 · 517.l

持续部署与交付最后一关不同

理解等级:中级

部署过程从编码延伸到真实用户在生产使用。全程自动化、没有人工干预是持续部署;自动化直到生产投放前,最终仍需人工放行,则是持续交付。区别在发布控制点,不代表持续交付没有自动测试。离线设备或高耦合生态未必适合随时独立发布,应按领域约束选择。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 可部署性 · 查看原书依据

      If this process is fully automated—that is, if there is no human intervention—then it is called continuous deployment. If the process is automated up to the point of placing (portions of) the system into production and human intervention is required (perhaps due to regulations or policies) for this final step, the process is called continuous delivery.

    参考来源

    - 位置:《Software Architecture in Practice, 4th Edition》第5章《可部署性》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch05.html) - 结论依据:原文的定义、机制或比较支持“部署过程从编码延伸到真实用户在生产使用”;正文保留其条件与取舍。 - 原始内容:If this process is fully automated—that is, if there is no human intervention—then it is called continuous deployment. If the process is automated up to the point of placing (portions of) the system into production and human intervention is required (perhaps due to regulations or policies) for this final step, the process is called continuous delivery.