Skip to content

ci(monorepo): make container deploys finish and verify the running image - #17

Merged
gustmrg merged 1 commit into
mainfrom
fix/backend-deploy-stdin
Oct 11, 2026
Merged

gustmrg merged 1 commit into
mainfrom
fix/backend-deploy-stdin

Conversation

@gustmrg

@gustmrg gustmrg commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Problem

The backend/v1.12.4 release (run 38062008463) reported a successful deploy, but production kept running the old backend container.

The remote deploy script is passed to bash -s on stdin. The docker compose run ... --migrate step inherited that stdin and consumed the rest of the script, so bash exited with code 0 right after the migrations. docker compose up never ran.

Changes

  • Run the migration with -T and </dev/null so the rest of the script still runs.
  • Start the backend and MCP server with up --wait so the deploy waits for the containers to be ready.
  • After starting, check that the running container uses the released image tag and fail the job if it doesn't.
  • Turn the one-line MCP deploy command into a script, matching the backend deploy.

- Keep the backend migration container from reading the deploy script on stdin, which ended the deploy before the API was recreated
- Wait for the backend and MCP server containers to be ready after starting them
- Fail the deploy when the running container does not use the released image
@gustmrg
gustmrg merged commit 4a21824 into main Oct 11, 2026
4 checks passed
@gustmrg
gustmrg deleted the fix/backend-deploy-stdin branch October 11, 2026 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant