ci: keep tests in CI and move image pushes to a local release script
The Gitea registry rejects kaniko pushes from job containers with 401 reqPackageAccess even though the same credentials work from a normal machine, so the image job could never go green. Drop the image job; CI now only runs unit tests, the smoke test and the Helm chart lint. Add scripts/release.sh, which builds and pushes the image from a trusted machine and can optionally apply the users secret and run helm upgrade.
This commit is contained in:
1 parent
9eed647df0
commit
60e8dadce6
3 files changed
+93
-55
No files matched your search
@@ -179,7 +179,7 @@ Build a lightweight, self-hosted **OpenSubsonic-compatible music server** in **K
|
||||
- **Transcoding:** `ffmpeg` binary in the runtime image (libmp3lame), invoked as a subprocess
|
||||
- **Logging:** `logback-classic` + `kotlin-logging-jvm`
|
||||
- **Config:** YAML (`library.yaml`, `users.yaml`) with env-var overrides for paths and secrets
|
||||
- **Deployment:** multi-stage Dockerfile, Helm chart for k3s, Gitea Actions for image builds
|
||||
- **Deployment:** multi-stage Dockerfile, Helm chart for k3s, Gitea Actions for tests, local release script for image pushes
|
||||
|
||||
---
|
||||
|
||||
@@ -630,18 +630,22 @@ Cover extraction order: embedded APIC frame -> `cover.jpg`/`folder.jpg`/`front.j
|
||||
- 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/taptap/audiomanager:<tag>` (registry paths must be lowercase).
|
||||
- Gitea Actions builds and pushes on tags; `imagePullSecret` is provided by the cluster.
|
||||
- Images are built and pushed from a trusted machine, not from Gitea Actions; `imagePullSecret` is provided by the cluster.
|
||||
|
||||
Build the image locally:
|
||||
Build and push the image:
|
||||
|
||||
```bash
|
||||
docker build -t gitea.tap-tap.win/taptap/audiomanager:dev .
|
||||
docker login gitea.tap-tap.win
|
||||
scripts/release.sh # tag = git short SHA, pushes :<sha> and :latest
|
||||
scripts/release.sh --tag v1.0.0 # explicit tag
|
||||
scripts/release.sh --deploy # also apply the users secret and helm upgrade
|
||||
```
|
||||
|
||||
`.gitea/workflows/ci.yaml` runs tests and the smoke script, then builds and pushes
|
||||
`:latest` for `main` and the tag name for `v*` tags. Set `REGISTRY_USERNAME` /
|
||||
`REGISTRY_PASSWORD` repository secrets if the automatically provided token cannot
|
||||
push to the registry.
|
||||
`.gitea/workflows/ci.yaml` only runs the test suite, the smoke script and the Helm
|
||||
chart lint. Image builds do not run in CI because the Gitea registry rejects
|
||||
pushes from job containers (`401 Unauthorized: reqPackageAccess`), while the same
|
||||
credentials work from a normal machine. Releases therefore stay a deliberate local
|
||||
step; `scripts/release.sh --deploy` covers build, push and `helm upgrade`.
|
||||
|
||||
### 9.2 Helm chart
|
||||
|
||||
|
||||
Reference in new issue
Block a user