ci: use a prebuilt image with every pipeline dependency
CI / test (push) Successful in 1m52s
CI / chart (push) Successful in 3s
CI / image (push) Failing after 2s

Add ci/Dockerfile (JDK 21, Gradle 8.14.3, ffmpeg, sqlite3, node,
docker CLI and Helm) and build it as taptap/audiomanager-ci. Workflows
now start from that image instead of downloading a JDK and installing
packages on every run.

The registry namespace is the lowercased package owner `taptap`, not
`tap-tap`; update the chart, workflow and documentation accordingly.
The image build uses plain docker build/push, since the job container
starts with no buildx plugin.
This commit is contained in:
TapTap committed 2026-11-13 13:37:15 +00:00
1 parent d812e7644f
commit 4c6f1c8fe8
6 files changed
+103 -38

No files matched your search

+3 -3
View File
@@ -629,13 +629,13 @@ Cover extraction order: embedded APIC frame -> `cover.jpg`/`folder.jpg`/`front.j
- Multi-stage Dockerfile: Gradle build -> glibc-based `eclipse-temurin:21-jre-jammy` with `ffmpeg` installed (Alpine/musl is unsupported by sqlite-jdbc's bundled native library).
- Runtime flags: `-XX:+UseSerialGC -Xmx256m` (adjustable via Helm).
- Non-root user (UID 10001), read-only root filesystem, `/tmp` as `emptyDir`, `/data` as PVC.
- Image: `gitea.tap-tap.win/tap-tap/audiomanager:<tag>` (registry paths must be lowercase).
- Image: `gitea.tap-tap.win/taptap/audiomanager:<tag>` (registry paths must be lowercase).
- Gitea Actions builds and pushes on tags; `imagePullSecret` is provided by the cluster.
Build the image locally:
```bash
docker build -t gitea.tap-tap.win/tap-tap/audiomanager:dev .
docker build -t gitea.tap-tap.win/taptap/audiomanager:dev .
```
`.gitea/workflows/ci.yaml` runs tests and the smoke script, then builds and pushes
@@ -731,7 +731,7 @@ Verify each step with `./gradlew test` and/or `curl`:
## 12. Open Items / Assumptions
1. **Gitea registry path:** image assumed to be `gitea.tap-tap.win/tap-tap/audiomanager` (lowercased repo `TapTap/AudioManager`).
1. **Gitea registry path:** image is `gitea.tap-tap.win/taptap/audiomanager` (lowercased package owner `taptap`).
2. **Vault layout:** the chart expects a secret with a `users.yaml` key. Exact Vault path/agent template is deployment-side and not part of the app.
3. **Per-user music roots:** Vault/config must contain one folder entry per user root (e.g. `/mnt/media/music/<user>`); there is no implicit path convention.
4. **hostPath without pinning:** requires `/mnt/media/music` and `/mnt/media/longform` to exist on every node that can schedule the pod. Add a `nodeSelector` later if that changes.