#release-engineering
1105 approved public terms with this tag.
机器辅助翻译草稿 (Chinese) for "Monitor Sticky Note Green Button Rule": Monitor Sticky Note Green Button Rule is a ci/cd vernacular term for preview deploy work in a policy-driven service network. It describes a green button rule that blocks risky work until the checks make sense, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Monitor Sticky Note Green Button Rule after the release plan slid like a lunch tray. Then the build passed for a real reason, not crossed fingers.”
机器辅助翻译草稿 (Chinese) for "Monitor Whiteboard Build Gate": Monitor Whiteboard Build Gate is a ci/cd vernacular term for artifact upload work in a policy-driven service network. It describes a build gate that blocks risky work until the checks make sense, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Monitor Whiteboard Build Gate after the route list looked like an open backpack. Then the agent showed its receipt and waited for a grown-up key.”
机器辅助翻译草稿 (Chinese) for "Monitor Whiteboard Discovery Map": Monitor Whiteboard Discovery Map is a policy-driven architecture vernacular term for trust policy work in a policy-driven service network. It describes a discovery map that makes public reads easy while keeping protected writes behind the platform key, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Monitor Whiteboard Discovery Map after the sitemap had a link that forgot where school was. Then the rollback was ready before the ship button got sweaty.”
机器辅助翻译草稿 (Chinese) for "Monitor Whiteboard Log Flashlight": Monitor Whiteboard Log Flashlight is a devops vernacular term for on-call handoff work in a policy-driven service network. It describes a log flashlight that keeps everyday operations boring in the best possible way, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Monitor Whiteboard Log Flashlight after the route list looked like an open backpack. Then the agent showed its receipt and waited for a grown-up key.”
机器辅助翻译草稿 (Chinese) for "Monitor Whiteboard Oops Plan": Monitor Whiteboard Oops Plan is a release engineering vernacular term for health probe work in a policy-driven service network. It describes a oops plan that ships changes in small, observable steps instead of one giant surprise, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Monitor Whiteboard Oops Plan after the agent reached for the big button too early. Then the docs, API, MCP, and policy files agreed.”
机器辅助翻译草稿 (Chinese) for "Monitor Whiteboard Protected Doorbell": Monitor Whiteboard Protected Doorbell is a policy-driven architecture vernacular term for trust policy work in a policy-driven service network. It describes a protected doorbell that connects service behavior to written policy instead of vibes, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Monitor Whiteboard Protected Doorbell after the release plan slid like a lunch tray. Then the build passed for a real reason, not crossed fingers.”
机器辅助翻译草稿 (Chinese) for "Monitor Whiteboard Route Passport": Monitor Whiteboard Route Passport is a policy-driven architecture vernacular term for llms index work in a policy-driven service network. It describes a route passport that connects service behavior to written policy instead of vibes, using source labels, trace links, route evidence, and public/protected boundaries that an operator or agent can follow.
“示例草稿: The team used Monitor Whiteboard Route Passport after the rollback plan hid under sticky notes. Then everyone knew the next check before the meeting got weird.”
Monorepo GitOps 是 GitOps 术语，用来说明 a GitOps layout where many services or environments live in one repository. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: OpenGitOps principles.
“团队午饭前用了 Monorepo GitOps，发布就没有系着松鞋带冲进生产环境。”
Notification Controller 是 GitOps 术语，用来说明 a Flux controller that sends events to external systems. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Flux documentation.
“团队午饭前用了 Notification Controller，发布就没有系着松鞋带冲进生产环境。”
OCIRepository Source 是 GitOps 术语，用来说明 a Flux source object that points to an OCI artifact repository. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Flux documentation.
“团队午饭前用了 OCIRepository Source，发布就没有系着松鞋带冲进生产环境。”
OPA Gatekeeper 是 GitOps 术语，用来说明 a Kubernetes policy system often used to enforce admission constraints. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Kubernetes controller pattern.
“团队午饭前用了 OPA Gatekeeper，发布就没有系着松鞋带冲进生产环境。”
Orphaned Resource 是 GitOps 术语，用来说明 a live object that is not clearly owned by the current desired source state. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Argo CD documentation.
“团队午饭前用了 Orphaned Resource，发布就没有系着松鞋带冲进生产环境。”
OutOfSync 是 GitOps 术语，用来说明 a status showing the live system does not match the desired source state. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Argo CD documentation.
“团队午饭前用了 OutOfSync，发布就没有系着松鞋带冲进生产环境。”
Overlay Patch 是 GitOps 术语，用来说明 a targeted change layered onto a base manifest. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Argo CD documentation; Flux documentation.
“团队午饭前用了 Overlay Patch，发布就没有系着松鞋带冲进生产环境。”
Owner Reference 是 GitOps 术语，用来说明 metadata linking a resource to the object that controls it. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Kubernetes controller pattern.
“团队午饭前用了 Owner Reference，发布就没有系着松鞋带冲进生产环境。”
Platform Repository 是 GitOps 术语，用来说明 a repository that stores shared platform services, policies, and add-ons. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: OpenGitOps principles.
“团队午饭前用了 Platform Repository，发布就没有系着松鞋带冲进生产环境。”
Policy as Code 是 GitOps 术语，用来说明 security, compliance, or release rules written as versioned machine-readable code. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: OpenGitOps principles.
“团队午饭前用了 Policy as Code，发布就没有系着松鞋带冲进生产环境。”
Preview Environment 是 GitOps 术语，用来说明 a temporary environment used to review a change before merge or release. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Argo CD documentation.
“团队午饭前用了 Preview Environment，发布就没有系着松鞋带冲进生产环境。”
Progressive Delivery 是 GitOps 术语，用来说明 releasing changes gradually while watching evidence and safety signals. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: Argo CD documentation.
“团队午饭前用了 Progressive Delivery，发布就没有系着松鞋带冲进生产环境。”
Promotion PR 是 GitOps 术语，用来说明 a pull request that moves a known change into the next environment. 它帮助团队、人和代理比较声明的源状态与正在运行的系统，再按证据行动，不把部署说成比实际更多。 来源: OpenGitOps principles.
“团队午饭前用了 Promotion PR，发布就没有系着松鞋带冲进生产环境。”