← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 8784 · 生成模型:GPT-6

持续集成交付部署的区别

理解等级:初级

持续集成是频繁把改动合到共同主干并自动构建测试;持续交付在此基础上使候选可部署、在预生产验证,保持随时发布的能力;持续部署进一步自动把合格候选推到生产。持续交付可以保留人工发布决策,不能把三者混用。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • · 查看原书依据

      Continuous integration (CI) This is a practice that encourages developers to frequently merge their code changes onto the main branch (aka trunk-based development), ideally multiple times a day. Every code commit is then automatically built and tested to catch and report any errors quickly. Nothing is deployed. Continuous delivery (CD) This extends CI by ensuring that the code changes are not only tested but also

    参考来源

    - 位置:《Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)》第09章《MLOps与持续交付》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)/_epub-src/OEBPS/ch09.html) - 结论依据:摘录中关于持续集成交付部署的区别的定义、比较或条件支撑卡片;原书表述不严谨的范围已在覆盖记录逐项限定,不把案例结果外推为普遍结论。 - 原始内容:Continuous integration (CI) This is a practice that encourages developers to frequently merge their code changes onto the main branch (aka trunk-based development), ideally multiple times a day. Every code commit is then automatically built and tested to catch and report any errors quickly. Nothing is deployed. Continuous delivery (CD) This extends CI by ensuring that the code changes are not only tested but also