ci: push images to artifactapi registry instead of gitea #2
Reference in New Issue
Block a user
Delete Branch "benvin/push-artifactapi"
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?
Why
Hard switch of this repo's container image push from the Gitea registry to the artifactapi local docker registry. The Gitea VM and its embedded registry are being retired, so images must publish to artifactapi's real Registry V2 instead; Ben chose a hard switch over dual-push.
Changes
.woodpecker/docker.yamlpush target atartifactapi.k8s.syd1.au.unkin.net/docker-internal/jellyfin-ha.droneci/DRONECI_PASSWORDcreds — artifactapi accepts unauthenticated in-cluster pushes..woodpecker/build.yamlto the same path.benvin/jellyfin-habranch, so this PR targets that branch, notmain.Takes effect on the next
v*tag — the docker pipeline only runs on tags.https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv
Superseded by #3, which stacks this artifactapi-push change on the build scaffolding plus a third commit repointing the build at the git.unkin.net/unkin/jellyfin-ha-src fork. Merging #3 alone carries all three commits. Closing.
Pull request closed