知识卡片
构建发布运行分成三阶段
构建固定代码与依赖生成制品;发布把该制品与目标配置结合成有唯一身份的版本;运行执行这个版本。环境变化通常应复用制品而改变配置,便于回滚和追溯。若每个环境重新编译,即使源码版本相同也增加了无法证明制品一致的差异。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- It’s All About Dependability · 查看原书依据
Typically this is accomplished in three distinct stages, illustrated in Figure 6-4 and described below: Build In the build stage, an automated process retrieves a specific version of the code, fetches dependencies, and compiles an executable artifact we call a build. Every build should always have a unique identifier, typically a timestamp or an incrementing
参考来源
- 位置:《Cloud Native Go》第06章《It’s All About Dependability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch06.xhtml)
- 结论依据:构建固定代码与依赖生成制品;发布把该制品与目标配置结合成有唯一身份的版本;运行执行这个版本。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:Typically this is accomplished in three distinct stages, illustrated in Figure 6-4 and described below: Build In the build stage, an automated process retrieves a specific version of the code, fetches dependencies, and compiles an executable artifact we call a build. Every build should always have a unique identifier, typically a timestamp or an incrementing