fix: deployment v0.1.6 cannot pull images after publication failure #12
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: WealthLedger/deploy#12
Reference in New Issue
Block a user
Server
./deploy.sh v0.1.6failed at preflight image pull. Existing frontend 1.2.0 and backend 2.2.0 were not stopped; backup none. Frontend tag-push image job 1614 failed at Nexus login:https://nexus.personal.ksv741.ru/v2/returned HTTP 404; frontend 1.2.1 was not published by that job. Backend image job 1616 was still in progress at investigation time.Related: frontend#21, backend#25, main#44, deploy#10. Deploy v0.1.6 was tagged before confirming image publication; do not retry until both pinned images exist and are pullable from the deployment host.
Acceptance criteria: identify and fix registry endpoint/publishing path with owners, publish and verify exact versioned images, then confirm deployment preflight succeeds. Keep existing data and immutable published tags intact.
После восстановления Nexus rerun публикации: frontend v1.2.1 job 1614 успешен (login и publish); backend v2.3.0 job 1616 прошёл login, verify/e2e, но сборка Docker упала до push: Dockerfile закрепляет
ca-certificates=20250419~deb12u1, которой уже нет в Debian bookworm apt index. Тег backend v2.3.0 и deploy v0.1.6 опубликованы и неизменяемы; rerun backend без изменения исходника не поможет. Для корректной поставки нужен новый backend tag с исправленным Dockerfile и новый deploy bundle tag. На локальном macOS Docker daemon недоступен; CI Linux остаётся местом проверки сборки.