<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Yunxiao Flow on 黄文卓 | DevOps Engineer</title>
    <link>https://socake.github.io/tags/yunxiao-flow/</link>
    <description>Recent content in Yunxiao Flow on 黄文卓 | DevOps Engineer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor>
    <webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster>
    <copyright>© 2026 Wenzhuo Huang</copyright>
    <lastBuildDate>Thu, 30 Apr 2026 12:00:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/tags/yunxiao-flow/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Playbook：CI/CD 流水线模板化——3 个标准模板覆盖 80% 服务的端到端实战</title>
      <link>https://socake.github.io/playbook/cicd-pipeline-templating/</link>
      <pubDate>Thu, 30 Apr 2026 12:00:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/playbook/cicd-pipeline-templating/</guid>
      <description>在 80+ 条流水线的体量下，每条服务自己拷一份 yaml 是工程债：字段命名漂移、改一次通知模板要改 80 处、新人不知道照哪条抄。本文把方案从「思路」推进到「拿来即用」：每个标准模板给完整 YAML（含 anchors / 变量组绑定 / 审批节点）、对应 GitHub Actions reusable workflow、Jenkins shared library；附 create-pipeline.sh 端到端脚本、变量组管理 API 调用、模板回归测试 dry-run；7 个云效官方文档不写的硬约束（schedule 不工作 / step envs 失效 / stage 间永远线性渲染等）每个含完整修复 + 通用结论。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/playbook/cicd-pipeline-templating/featured.jpg" />
    </item>
    
  </channel>
</rss>
