git-echo/linux_patch_manager
Private
Public Access
1
0
Fork 0
Code Releases 8 Wiki Activity

feat: Add Gitea Actions CI/CD pipeline for automated .deb builds
Some checks failed
Build .deb Package / build-backend (push) Has been cancelled
Details
Build .deb Package / build-frontend (push) Has been cancelled
Details
Build .deb Package / build-deb (push) Has been cancelled
Details

Browse Source 
- .gitea/workflows/build.yml: 3-job pipeline (backend, frontend, package)
- Builds on Ubuntu 24.04 container for correct glibc
- Tags v* trigger release + .deb upload to Gitea Releases
- Master pushes produce dev builds as artifacts
- tasks/lessons.md: CI/CD-first lesson captured
This commit is contained in:
Echo
2026-04-24 01:12:34 +00:00
parent 4e992afacc
commit c31fc0e6e0
2 changed files with 241 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
tasks/lessons.md Normal file
View File

@ -0,0 +1,11 @@
# Linux Patch Manager — Lessons Learned
## 2026-04-24: CI/CD First, Not Manual Builds
**Pattern:** When creating release packages, set up CI/CD pipeline (Gitea Actions) FIRST before manually building.
**Why:** Manual builds are one-off and not reproducible. CI/CD ensures every push/tag produces a fresh, consistent package built on the correct target OS (Ubuntu 24.04), with proper glibc compatibility.
**Action:** Always create `.gitea/workflows/` pipeline for automated builds. Use `scripts/build-package.sh` only for local dev testing.
## 2026-04-24: Verify Runner Before Workflow
**Pattern:** Before creating Gitea Actions workflows, verify the act-runner is registered and online.
**Why:** A workflow file without a running runner is dead code. The runner at gitea-runner-lxc.moon-dragon.us needs to be verified as operational.
**Action:** Check runner status via Gitea API (`/api/v1/repos/echo/linux_patch_manager/actions/runners`) or web UI before assuming CI/CD will work.