ci: compress to 4-job pipeline (single deploy job, test -> prod) #134
No reviewers
Labels
No labels
architecture
backend
bug
ci
config
database
docker
documentation
duplicate
enhancement
frontend
help wanted
invalid
issue-25
issue-26
issue-42
issue-65
issue-67
issue-82
migrations
p0-critical
p1-high
p2-medium
p3-low
performance
quality
question
security
state-management
testing
timezone
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fastie81/honbu-manager!134
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/compress"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Compress the CI to a 4-job pipeline: test, lint-frontend, build, and a single deploy job.
deploy deploys the SAME image to the TEST node on main pushes, and promotes that identical image to PROD on v tags (conditional step), bound to -p honbu-manager-production with TUNNEL_TOKEN + Google secrets injected from Forgejo secrets. This replaces the separate deploy-test/deploy-prod jobs (-48 lines).
The runner (.33, Podman, global registration 'Proxmox-LXC') auto-mounts podman.sock at /var/run/docker.sock in job containers, so the workflow no longer needs an explicit socket mount.
Verified green on this branch: test 2m28s, lint 1m22s, build 2m29s (deploy correctly skipped on a non-main branch push). A v-tag run will exercise the full test->prod promotion.