Merge pull request 'Fix GitOps redeploy race: chain to end of build, not a parallel webhook' (#7 ) from fix/chain-portainer-redeploy-after-build into main

Reviewed-on: #7
Chain Portainer redeploy to the end of the build workflow, not a parallel webhook
2026-08-23 15:12:03 +00:00 · 2026-08-23 15:11:31 +00:00
1 changed files with 7 additions and 0 deletions
@@ -31,3 +31,10 @@ jobs:
          IMAGE="${{ vars.REGISTRY_HOST }}/${{ gitea.repository }}/claude-agent:latest"
          docker build -t "$IMAGE" ./agent
          docker push "$IMAGE"
+
+      - name: Trigger Portainer redeploy
+        # Deliberately NOT a separate Gitea repo webhook firing in parallel on the same
+        # push — that raced with this build and could redeploy before the new image was
+        # actually pushed, silently keeping the old code running. Chaining it here as the
+        # last step guarantees the image exists before Portainer goes to pull it.
+        run: curl -f -X POST "${{ secrets.PORTAINER_WEBHOOK_URL }}"
Author	SHA1	Message	Date
william	4fc4433833	Merge pull request 'Fix GitOps redeploy race: chain to end of build, not a parallel webhook' (#7 ) from fix/chain-portainer-redeploy-after-build into main build-agent / build-and-push (push) Successful in 3s Details Reviewed-on: #7	2026-08-23 15:12:03 +00:00
william	8db8347df0	Chain Portainer redeploy to the end of the build workflow, not a parallel webhook The separate Gitea push webhook to Portainer fired in parallel with this build workflow on the same push event, so it could redeploy before the new image finished pushing — Portainer would then pull the still-current :latest tag and silently keep running old code. Removed that webhook; redeploy now only happens as this workflow's last step, after the image push actually completes.	2026-08-23 15:11:31 +00:00