Repository navigation
ci(deploy): deploy the US and EU instances in parallel - #1962
Conversation
The EU deploy waited on the US one, doubling prod deploy time. Each instance has its own stage, environment and database, so they can run side by side once the shared ingest binary is built.
Maple review🟢 Confidence 10/10 · safe to merge
What was checked
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 27 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
deploy-prd-eunow needs onlyingest-binary, so the EU instance deploys alongside US instead of after it.Trade-off
The sequencing acted as a canary only for deploy-time failures (Alchemy deploy, migrations, the revision check). A broken migration or failed deploy now reaches both instances. Runtime bugs were never caught by it, since EU started as soon as US went green.
Test plan
ingest-binaryanddeployment-gatereports both results.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.