知识卡片
一次构建多次部署
一次构建、多次部署是每次提交只解析一次构建依赖,把同一构建送入各环境;每次部署只补实例配置。若每次部署重新解析依赖,测试与生产可能得到不同版本,故障难以重现。同一代码提交本身不足以证明环境一致,构建依赖也须固定。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建与分发基础设施代码 · 查看原书依据
A more rigorous approach to ensuring consistency across environments is to separate the Assemble step and run it once for each commit, in the build stage. Then run the Compile step, with deployment-specific activities, each time the build is deployed. Figure 15-4 illustrates this. Figure
参考来源
- 位置:《Infrastructure As Code》第15章《构建与分发基础设施代码》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch15.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“一次构建、多次部署是每次提交只解析一次构建依赖,把同一构建送入各环境;每次部署只补实例配置”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:A more rigorous approach to ensuring consistency across environments is to separate the Assemble step and run it once for each commit, in the build stage. Then run the Compile step, with deployment-specific activities, each time the build is deployed. Figure 15-4 illustrates this. Figure