SHA256
deploy / deploy (push) Skipped
按 deploy/ci-cd.md 方案把除推送触发之外的东西都准备好:
- customization/check.sh <base-url>: 把 preview.sh check 里的"定制生效"断言抽成
任意实例可跑的脚本(首页/页脚/meta/官网链接/登录页两张卡/无通行密钥方框/
无「工单」/无 example.com), 另加生产才有的 OIDC 入口 307 断言(404 = 认证源没注册上)。
实测对生产 17/17 通过。
- deploy/scripts/auto-deploy.sh: build.py -> compose up -d -> verify.sh + check.sh,
失败自动回滚到 deploy/.state/last-deployed; flock 串行; 结束时把 clone 所有权还给
ymy(job 容器里是 root); 内网验证强制不走代理。
- deploy/runner/{compose.yaml,config.yaml,.env.example}: act_runner v0.6.1 跑在容器里
(不需要 root), network: host + 同路径挂载部署克隆 + 宿主 docker CLI/compose 插件,
capacity 1 保证部署串行。
- .gitea/workflows/deploy.yml: push main + workflow_dispatch, [skip deploy] 跳过,
concurrency 串行, 只做"同步到 github.sha + 调 auto-deploy.sh"。
- .gitignore: deploy/.state/、deploy/runner/{.env,data/}。
依据见 deploy/ci-cd.md(含全部实测证据与待确认项)。
41 lines
1.2 KiB
YAML
41 lines
1.2 KiB
YAML
# main 推送后自动部署到 10.80.42.185/QA。
|
|
# 逻辑都在 deploy/scripts/auto-deploy.sh 里, 这里只负责"同步到目标提交 + 调脚本"。
|
|
# 详见 deploy/ci-cd.md。
|
|
name: deploy
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
workflow_dispatch:
|
|
|
|
concurrency:
|
|
group: deploy-main
|
|
cancel-in-progress: false
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
deploy:
|
|
# 只认 main 的 push 或手动触发; 提交信息含 [skip deploy] 则跳过
|
|
if: >-
|
|
github.event_name == 'workflow_dispatch' ||
|
|
(github.ref == 'refs/heads/main' &&
|
|
!contains(github.event.head_commit.message, '[skip deploy]'))
|
|
runs-on: self-hosted
|
|
timeout-minutes: 30
|
|
steps:
|
|
- name: 同步到目标提交
|
|
run: |
|
|
set -euo pipefail
|
|
cd /home/ymy/deploy/tjhlp-gitea
|
|
git fetch --prune origin
|
|
# -f: 部署克隆是 CI 独占的; 上一个已部署版本的 deploy/runner/* 等文件在本版本
|
|
# 若已被跟踪, 会作为"未跟踪文件"挡住普通 checkout(实测)
|
|
git checkout -f --detach "${{ github.sha }}"
|
|
git --no-pager log --oneline -1
|
|
- name: 构建并部署(失败自动回滚)
|
|
run: |
|
|
set -euo pipefail
|
|
./deploy/scripts/auto-deploy.sh
|