a year ago
Hi! I'd like to know if it's possible to 'sync' the deployment of a service, either deploying all of them or making all of them fail (sort of like a 'transaction').
Right now, my project is hosted in a GitHub monorepo and pushing to it deploys both the frontend and the backend. The issue is, if one of the deployments fail for some reason (e.g. linting errors or build issues), the failed service will be running an older version of the application, yet the other service may still be deployed successfully with a new version. This could cause, for instance, the frontend to try to access routes that don't exist in the deployed backend.
(Also, even if both deployments happen successfully, if the deployment times are different for each service, each of them will briefly be running different versions, which may also be a problem.)
10 Replies
a year ago
333f0a15-0fd0-46be-8d54-a043c9893a2e
a year ago
I imagine this must be possible with something like GitHub Actions, but I'd like to know in advance before trying to implement it.
a year ago
sorry we don't provide native functionality for this right now
a year ago
I see, so I guess the best solution would be to be wary of this and try to make updates 'backward-compatible'
a year ago
Does there happen to be plans to build such a feature? 👀
a year ago
yeah that would be the best course of action
a year ago
there doesn't, sorry
a year ago
alrighty, thanks a lot! 🙂
a year ago
no problem!
a year ago
!s
Status changed to Solved brody • about 1 year ago