2 years 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
2 years ago
333f0a15-0fd0-46be-8d54-a043c9893a2e
2 years 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.
2 years ago
sorry we don't provide native functionality for this right now
2 years ago
I see, so I guess the best solution would be to be wary of this and try to make updates 'backward-compatible'
2 years ago
Does there happen to be plans to build such a feature? 👀
2 years ago
yeah that would be the best course of action
2 years ago
there doesn't, sorry
2 years ago
alrighty, thanks a lot! 🙂
2 years ago
no problem!
2 years ago
!s
Status changed to Solved brody • over 1 year ago