Brad Rodgers b9f2c72bd4
All checks were successful
CI / ci (push) Successful in 1m55s
deploy: private package pull via External Secrets; pull over public HTTPS (no k3s restart)
- k3s pulls git.7tl-homelab.com/... over valid TLS (no registries.yaml/node config)
- CI still pushes internally to 10.66.15.22:3000 (fast, insecure-trusted)
- ExternalSecret materializes gitea-registry dockerconfigjson from OpenBao
- deployment uses imagePullSecrets: gitea-registry
- .env added to .dockerignore
2026-07-17 07:36:22 -04:00

101 lines
4.6 KiB
YAML

# BlueCap Strategies CI — Gitea Actions (ADR-0007)
#
# Pipeline: install → build (typecheck) → seo:lint → e2e → build & push image to Gitea Packages
# → bump the image tag in k8s/ and commit back to main. ArgoCD then reconciles k3s.
#
# PREREQUISITES (homelab, verify before the first run — see docs/gitops-deployment-strategy.md):
# 1. Docker must be usable from the job container. The runner mounts /var/run/docker.sock; if
# jobs can't see it, enable socket passthrough in act_runner config or switch this to kaniko.
# 2. The RUNNER HOST's dockerd must treat 10.66.15.22:3000 as an insecure (HTTP) registry
# ("insecure-registries": ["10.66.15.22:3000"] in /etc/docker/daemon.json).
# 3. K3S must trust the same HTTP registry — add a registries.yaml entry (k3s_registry_mirrors)
# for 10.66.15.22:3000, then restart k3s, or the pods can't pull the image.
# 4. The Gitea container package should be PUBLIC (simplest). If PRIVATE, add an imagePullSecret
# (see k8s/deployment.yaml) and grant the run token package:write.
# 5. secrets.GITEA_TOKEN (auto-injected per run) needs write access to this repo (tag-bump commit)
# and the package registry.
name: CI
on:
push:
branches: [main]
# Don't re-trigger on the CI tag-bump commit (touches k8s/) or docs-only changes.
paths-ignore:
- 'k8s/**'
- 'docs/**'
- 'planning/**'
- '**/*.md'
env:
# Push over the internal HTTP endpoint (fast, no edge; host dockerd trusts it as insecure).
PUSH_IMAGE: 10.66.15.22:3000/bmr_bluecap/bcs-website
# k3s pulls over the public HTTPS endpoint (valid TLS -> no registries.yaml / node config / restart).
# Same Gitea package as PUSH_IMAGE, just a different access path.
DEPLOY_IMAGE: git.7tl-homelab.com/bmr_bluecap/bcs-website
jobs:
ci:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set up Node 22
uses: actions/setup-node@v4
with:
node-version: 22
- name: Install dependencies
run: npm ci
- name: Build (typecheck + astro build)
run: npm run build
- name: SEO lint
run: npm run seo:lint
# Playwright e2e (headless Chrome) is intentionally NOT run in CI — it's the heaviest step and
# adds little for a static site over `astro build` + seo:lint. Run it locally: `npm run test:e2e`.
- name: Compute image tag
id: tag
run: echo "sha=$(echo ${{ github.sha }} | cut -c1-12)" >> "$GITHUB_OUTPUT"
- name: Ensure docker + kustomize are available
run: |
command -v docker >/dev/null 2>&1 || { apt-get update && apt-get install -y docker.io; }
command -v kustomize >/dev/null 2>&1 || \
curl -sSL "https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv5.4.3/kustomize_v5.4.3_linux_amd64.tar.gz" \
| tar xz -C /usr/local/bin
# CI_TOKEN: a Gitea Personal Access Token (scopes: write:package, write:repository) owned by
# the repo owner, stored as a repo Actions secret. The auto GITEA_TOKEN lacks reliable package
# scope on Gitea, hence a dedicated PAT for both the registry push and the tag-bump commit.
- name: Build & push image to Gitea Packages
run: |
echo "${{ secrets.CI_TOKEN }}" | docker login 10.66.15.22:3000 -u "${{ github.repository_owner }}" --password-stdin
docker build -t "$PUSH_IMAGE:${{ steps.tag.outputs.sha }}" -t "$PUSH_IMAGE:latest" .
# Registry pushes can time out on a slow blob; docker push is resumable, so retry.
push_retry() {
for i in 1 2 3 4 5; do
docker push "$1" && return 0
echo "push of $1 failed (attempt $i), retrying in 10s..."
sleep 10
done
return 1
}
push_retry "$PUSH_IMAGE:${{ steps.tag.outputs.sha }}"
push_retry "$PUSH_IMAGE:latest"
- name: Bump k8s image tag and commit back
run: |
git config user.name "gitea-actions[bot]"
git config user.email "gitea-actions@bmr_bluecap"
# Deployment references the public HTTPS image (what k3s pulls); bump its tag.
(cd k8s && kustomize edit set image "$DEPLOY_IMAGE=$DEPLOY_IMAGE:${{ steps.tag.outputs.sha }}")
git add k8s/kustomization.yaml
git diff --cached --quiet && { echo "no image change"; exit 0; }
git commit -m "ci: deploy ${{ steps.tag.outputs.sha }} [skip ci]"
git remote set-url origin "http://${{ github.repository_owner }}:${{ secrets.CI_TOKEN }}@10.66.15.22:3000/bmr_bluecap/bcs-website.git"
git push origin HEAD:main