# ============================================================================ # .drone.yml — MixingX 交付晋级流水线(release-promote)— 本仓库第一条流水线 # # 触发方式: 手动 (Drone Web 界面 → 打开 mixingx.deploy → NEW BUILD) # 参数(可选,均有默认;Drone custom build 参数以同名环境变量注入各 step): # RELEASE_VERSION — 交付版本号 v1.0.1;不传则自动递增 patch(查 chart 仓库上一个 tag); # 可显式指定已存在版本(幂等复用,同版本发多客户) # CUSTOMER — 客户目录名,默认 mxlexus(唯一客户时可省略) # PLAN — 按服务交付计划(JSON 数组,每服务一条),示例: # [{"service":"sso","action":"deliver","harborTag":"develop-v.1.0.1-202608250629-41"}, # {"service":"agent","action":"reuse","version":"v1.0.1"}, # {"service":"ultra","action":"keep"}] # service: gateway/sso/ultra/audit/agent/edge; # action: keep(缺省)/reuse(复用已交付版本)/deliver(交付 Harbor tag, # 缺省取 demo 当前)/ci-now(行为同 deliver,release-notes 记为 ci-now) # SERVICES — 兼容参数,逗号分隔服务名 = 这些服务 deliver(其余 keep) # IMAGES — 兼容参数,逗号分隔 svc=harborTag = 该服务 deliver 且显式指定 tag # (PLAN 存在时优先于 SERVICES/IMAGES;全空 = 6 服务全量交付,与改造前一致) # CHART_ONLY — true 时只发 chart:跳过镜像基线与 retag,pin 只动 chart # targetRevision 与 release-notes,默认 false # RELEASE_NOTES — 发布说明,写入客户 release-notes.yaml,默认空 # DB_CHANGE — 逗号分隔服务名,本次含 DB 变更(须为本次非 keep 服务的子集),默认空 # OPERATOR — 发布操作人,默认 drone # PROMOTE_PROTOCOLS — true 时连 protocol mock 镜像一起晋级,默认 false(现场不部署) # # 职责(四步,详见 ci/promote.sh;按服务部分交付设计见 hub docs/adr/0074): # prepare: 解析 PLAN/版本号 + 生成交付基线 + 核对交付镜像清单 # retag : 基线镜像 develop-* → v1.0.x,bit 级复制推 ACR(ADR-0067,部分交付见 # hub docs/adr/0074),逐镜像记录 digest # chart : chart 仓库 bump Chart.yaml + 打 tag chart-v1.0.x(已存在则复用跳过; # 纯复用发布整步跳过) # pin : release 分支客户目录按服务钉版(镜像 tag + chart tag) + release-notes.yaml # # 边界: # - 不构建任何镜像(构建属于 9 个源码仓库的流水线) # - 不触碰 deploy master(demo 写回由构建流水线负责) # - git push 凭证走 Drone netrc 自动注入;推 ACR 走 secrets(acr_push_*) # - 凭证禁止走构建参数(会明文进构建历史,ADR-0066) # # Secrets (Drone → mixingx.deploy → Settings → Secrets): # acr_push_username / acr_push_password — ACR 推送凭证(✅ 已配置) # harbor_username / harbor_password — Harbor 凭证(prepare 校验显式 harborTag 存在性; # 未配置则跳过校验并警告) # ============================================================================ kind: pipeline type: docker name: release-promote trigger: event: - custom # 仅手动触发;push 事件(demo 写回)不触发任何东西 steps: # ═══════════════════════════════════════════ # Step 1: 准备 — 解析 PLAN + 版本号 + 交付基线 + 镜像清单核对 # ═══════════════════════════════════════════ - name: prepare image: 192.168.1.119:8888/mixingx/gitops-tools:latest pull: if-not-exists environment: HARBOR_USER: from_secret: harbor_username HARBOR_PASS: from_secret: harbor_password commands: - sh ci/promote.sh prepare # ═══════════════════════════════════════════ # Step 2: 镜像晋级 — pull 119 → tag ACR → push + 记录 digest # ═══════════════════════════════════════════ - name: retag-images image: docker:24-dind pull: if-not-exists privileged: true volumes: - name: dockersock path: /var/run/docker.sock environment: ACR_USER: from_secret: acr_push_username ACR_PASS: from_secret: acr_push_password ACR_REGISTRY: mx-imserver-registry.cn-shanghai.cr.aliyuncs.com HARBOR_REGISTRY: 192.168.1.119:8888/mixingx commands: - sh ci/promote.sh retag # ═══════════════════════════════════════════ # Step 3: chart 版本化 — bump Chart.yaml + tag chart-v1.0.x(已存在则复用) # ═══════════════════════════════════════════ - name: chart-tag image: 192.168.1.119:8888/mixingx/gitops-tools:latest pull: if-not-exists commands: - sh ci/promote.sh chart # ═══════════════════════════════════════════ # Step 4: 交付分支钉版 — release 分支客户目录按服务钉版 + release-notes # ═══════════════════════════════════════════ - name: pin-release image: 192.168.1.119:8888/mixingx/gitops-tools:latest pull: if-not-exists commands: - sh ci/promote.sh pin volumes: - name: dockersock host: path: /var/run/docker.sock