fix: dispatch dev/master deploys to split sysblokbot-testing/prod services#465
Merged
Merged
Conversation
…vices sysblok-infra now treats sysblokbot-prod and sysblokbot-testing as independent deploy targets (separate Compose projects) instead of one shared project that got force-recreated on every deploy, restarting prod on dev-only pushes. Point each workflow's repository_dispatch at its own service name to match. Do not merge until the sysblok-infra side (branch fix/split-sysblokbot-deploy-services there) is deployed and the one-time data migration to the new /srv/sysblokbot-prod and /srv/sysblokbot-testing paths is done -- merging first would dispatch deploys to service directories that don't exist yet on the host. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
publish_dev.ymlandpublish_master.ymlboth dispatched{"service": "sysblokbot"}tosysblok-infraregardless of branch, and that repo'sdeploy.ymlforce-recreates every container in thesysblokbotCompose project on every deploy — so adev-only push (testing image only) was restarting the live prod bot too.publish_dev.ymlnow dispatchesservice: sysblokbot-testing;publish_master.ymlnow dispatchesservice: sysblokbot-prod, matching the split done in sysblok/sysblok-infra#32.Depends on sysblok/sysblok-infra#32, which itself needs a one-time manual data migration on the Hetzner host before it's deployed. Merging this first would make the next
dev/masterpush dispatch to a service directory that doesn't exist yet on the infra side. Merge only after that PR is merged, the host migration is done, and both bots are confirmed healthy at their new/srv/sysblokbot-prod//srv/sysblokbot-testingpaths.Test plan
devafter merging, confirm onlysysblokbot-testingrestarts (check container uptime/logs),sysblokbot-produnaffected🤖 Generated with Claude Code