知识卡片

普通读书笔记卡 · 1903.c.3.a.1

修复重新进入流水线

理解等级:中级

在下游环境发现问题,可以直接试验以诊断,但正式修复应回到源代码,并从流水线开头重新验证。若把下游修复直接继续发布,它会绕过上游检查;若不回写源代码,后续发布又会覆盖修复。紧急状态也需要尽快恢复这条一致证据链。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 核心基础设施交付工作流 · 查看原书依据

      When using a code-driven, pipeline-managed delivery process, every change should be made to the source and pushed through the pipeline from the beginning. No changes should be made to application, infrastructure, or other elements of the system anywhere other than at the start of the pipeline. When you discover an issue in a later stage

    参考来源

    - 位置:《Infrastructure As Code》第14章《核心基础设施交付工作流》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch14.html) - 结论依据:原文说明在下游环境发现问题,可以直接试验以诊断,但正式修复应回到源代码,并从流水线开头重新验证;本卡据此解释其用途及适用边界。 - 原始内容:When using a code-driven, pipeline-managed delivery process, every change should be made to the source and pushed through the pipeline from the beginning. No changes should be made to application, infrastructure, or other elements of the system anywhere other than at the start of the pipeline. When you discover an issue in a later stage