Files

205 lines
8.5 KiB
YAML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
name: lpt-android Build
on:
workflow_dispatch:
inputs:
environment:
description: '构建环境(dev 仅允许 dev 分支;prod 仅允许 master 分支)'
required: true
type: choice
options:
- dev
- prod
env:
APP: lpt-android
REPO_URL: https://git.cat-shark.xyz/cat-shark/lpt-android.git
# 各环境的默认 API 地址。必须与 app/src/main/java/com/catshark/lpt/data/ApiClient.kt
# 里的 DEFAULT_BASE_URL 保持一致——第二步会逐字比对。
DEV_API: https://lpt-dev.cat-shark.xyz/api
PROD_API: https://lpt.cat-shark.xyz/api
# 上传 Release 附件需要写权限。Gitea 会给每个 job 注入一个仓库范围的 GITEA_TOKEN,
# 它的权限由这里声明(再受实例最大值限制)。
permissions:
contents: write
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: 校验分支 ↔ 环境
run: |
set -euo pipefail
REF="${{ gitea.ref }}"
BRANCH="${REF#refs/heads/}"
if [[ "$REF" == refs/tags/* ]]; then
echo "ERROR: 请从分支触发构建,不要用 tag。当前 ref=$REF"
exit 1
fi
ENV="${{ inputs.environment }}"
echo "branch=$BRANCH environment=$ENV sha=${{ gitea.sha }}"
case "$ENV" in
prod)
case "$BRANCH" in
master) echo "OK: prod 允许从 $BRANCH 构建" ;;
*)
echo "ERROR: prod 只能从 master 构建,当前分支是 '$BRANCH'"
echo "请切换到 master 后再 Run workflow,并选择 environment=prod"
exit 1
;;
esac
;;
dev)
case "$BRANCH" in
dev) echo "OK: dev 允许从 $BRANCH 构建" ;;
*)
echo "ERROR: dev 只能从 dev 分支构建,当前分支是 '$BRANCH'"
echo "请切换到 dev 后再 Run workflow,并选择 environment=dev"
exit 1
;;
esac
;;
*)
echo "ERROR: 未知 environment=$ENV"
exit 1
;;
esac
- name: Checkout code
run: |
set -euo pipefail
git clone "$REPO_URL" .
git checkout "${{ gitea.sha }}"
- name: 校验代码里的默认环境地址
run: |
set -euo pipefail
ENV="${{ inputs.environment }}"
ACTUAL="$(grep -oE 'DEFAULT_BASE_URL = "[^"]+"' app/src/main/java/com/catshark/lpt/data/ApiClient.kt \
| head -1 | sed 's/.*= "//; s/"$//')"
if [ "$ENV" = "prod" ]; then EXPECT="$PROD_API"; else EXPECT="$DEV_API"; fi
echo "代码里的分支默认地址 = $ACTUAL"
echo "本环境期望的地址 = $EXPECT"
if [ "$ACTUAL" != "$EXPECT" ]; then
echo "ERROR: $ENV 的默认 API 地址与分支不匹配。"
echo "这两个分支只允许差这一行:dev 指向 dev 环境、master 指向生产环境。"
exit 1
fi
echo "OK: 默认地址与环境匹配"
- name: 构建 APK(容器内完成,JDK/SDK 版本固化)
run: |
set -euo pipefail
docker build -f ci/Dockerfile -t lpt-android-apk:ci .
- name: 取出 APK 并打印校验值
run: |
set -euo pipefail
ENV="${{ inputs.environment }}"
SHORT="$(echo "${{ gitea.sha }}" | cut -c1-8)"
NAME="lpt-android-${ENV}-${SHORT}.apk"
docker create --name lpt-apk-out lpt-android-apk:ci > /dev/null
docker cp lpt-apk-out:/out/app-debug.apk "$NAME"
docker rm -f lpt-apk-out > /dev/null
ls -l "$NAME"
sha256sum "$NAME" | tee apk-sha256.txt
- name: 上传 APK 到 Release 附件
env:
TOKEN: ${{ secrets.GITEA_TOKEN }}
GITEA_REF: ${{ gitea.ref }}
ENV_NAME: ${{ inputs.environment }}
SHA: ${{ gitea.sha }}
run: |
set -euo pipefail
# runner 上只有 coreutils / grep / curl:不得依赖 python3、jq、node
# (历史上这三个都缺过:JS action 报 node,本步曾报 python3)
for t in curl grep cut head sed mktemp; do
command -v "$t" > /dev/null || { echo "ERROR: runner 缺少命令 $t"; exit 1; }
done
if [ -z "${TOKEN:-}" ]; then
echo "ERROR: GITEA_TOKEN 为空——本步骤依赖 Gitea 为每个 job 自动注入的仓库令牌"
exit 1
fi
API="https://git.cat-shark.xyz/api/v1/repos/cat-shark/lpt-android"
BRANCH="${GITEA_REF#refs/heads/}"
TAG="android-${ENV_NAME}"
ASSET="lpt-android-${ENV_NAME}.apk"
SHORT="$(echo "$SHA" | cut -c1-8)"
APK="lpt-android-${ENV_NAME}-${SHORT}.apk"
test -f "$APK"
AUTH=(-H "Authorization: token ${TOKEN}")
# 纯 shell 取 JSON 字段(不依赖 python3/jq)。
# 正则对空白宽容(Gitea 默认是紧凑 JSON,但保留容错以便任何重编码都不影响)。
# 找不到时返回空(`|| true`),否则 set -e 会直接中断。
name_re() { printf '%s' "$1" | sed 's/[.[\*^$()+?{}|]/\\&/g'; }
first_id() { grep -oE '"id"[[:space:]]*:[[:space:]]*[0-9]+' | head -1 | grep -oE '[0-9]+' | head -1 || true; }
asset_id() {
grep -oE '\{[[:space:]]*"id"[[:space:]]*:[[:space:]]*[0-9]+[[:space:]]*,[[:space:]]*"name"[[:space:]]*:[[:space:]]*"[^"]*"' \
| grep -E "\"name\"[[:space:]]*:[[:space:]]*\"$(name_re "$1")\"" \
| head -1 \
| sed -E 's/^\{[[:space:]]*"id"[[:space:]]*:[[:space:]]*([0-9]+).*/\1/' || true
}
# 1) 找滚动 release(看状态码而不是解析错误体);不存在就创建
REL_JSON="$(mktemp)"
CODE="$(curl -sS -o "$REL_JSON" -w '%{http_code}' "${AUTH[@]}" "$API/releases/tags/$TAG")"
echo "查 $TAG: HTTP $CODE"
if [ "$CODE" = "200" ]; then
RID="$(cat "$REL_JSON" | first_id)"
else
RID=""
fi
if [ -z "$RID" ]; then
echo "创建滚动 release: $TAG(分支 $BRANCH)"
curl -fsS "${AUTH[@]}" -H 'Content-Type: application/json' -X POST "$API/releases" \
-d "{\"tag_name\":\"$TAG\",\"target_commitish\":\"$BRANCH\",\"name\":\"LPT Android ${ENV_NAME}(滚动发布)\",\"body\":\"附件始终是该环境最新一次构建,每次覆盖;sha256 见对应构建日志。\"}" \
-o "$REL_JSON"
RID="$(cat "$REL_JSON" | first_id)"
if [ -z "$RID" ]; then
echo "ERROR: 创建 release 后拿不到 id,响应前 300 字节:"
head -c 300 "$REL_JSON"; echo
exit 1
fi
fi
echo "release id=$RID"
# 2) 同名附件先删,保证下载链接稳定
ASSETS_JSON="$(mktemp)"
curl -fsS "${AUTH[@]}" "$API/releases/$RID/assets" -o "$ASSETS_JSON"
for NAME in "$ASSET" "${ASSET}.sha256"; do
AID="$(cat "$ASSETS_JSON" | asset_id "$NAME")"
if [ -n "$AID" ]; then
echo "删除旧附件 $NAME (id=$AID)"
curl -fsS "${AUTH[@]}" -X DELETE "$API/releases/assets/$AID" > /dev/null
fi
done
# 3) 上传新附件
curl -fsS "${AUTH[@]}" -X POST "$API/releases/$RID/assets?name=$ASSET" \
-F "attachment=@${APK}" > /dev/null
curl -fsS "${AUTH[@]}" -X POST "$API/releases/$RID/assets?name=${ASSET}.sha256" \
-F "attachment=@apk-sha256.txt" > /dev/null
# 4) 回读校验:两个附件名都能在 release 上找到(不依赖任何外部工具)
curl -fsS "${AUTH[@]}" "$API/releases/$RID/assets" -o "$ASSETS_JSON"
MISSING=0
for NAME in "$ASSET" "${ASSET}.sha256"; do
if grep -qE "\"name\"[[:space:]]*:[[:space:]]*\"$(name_re "$NAME")\"" "$ASSETS_JSON"; then
echo "OK: 已上传 $NAME"
else
echo "ERROR: 附件 $NAME 上传后读不到"; MISSING=1
fi
done
if [ "$MISSING" != "0" ]; then
echo "release 附件列表响应:"; head -c 500 "$ASSETS_JSON"; echo
exit 1
fi
echo "OK: https://git.cat-shark.xyz/cat-shark/lpt-android/releases/tag/$TAG"
echo "附件: $ASSET / ${ASSET}.sha256(本次 sha=${SHORT})"