CI Workflows
I have successfully come up with a railway workflow.
But as we all know, there’s two errors that we often get on railway:
- build error (in this case Railway simply rolls back to the previous deployment)
- deploy error (in this case our app breaks entirely and there’s no rollback)
My workflow is definitely able to catch build errors.
However, I would love to investigate whether it can also catch deploy errors that lead to app crashing.
Anyone can help with this?
I am using the railway/cli tool to build this workflow and testing on an app that crashes.
6 Replies
Project ID:
dd81969e-e286-4d85-85de-40e92325591fdd81969e-e286-4d85-85de-40e92325591f
However, I would love to investigate whether it can also catch deploy errors that lead to app crashing.Railway will restart your app if it crashes, but this can't prevent critical unrecoverable crashes, in that case you will want to use a staging environment with end-2-end testing so that you can catch critical errors before pushing to production.
Thanks @Brody,
essentially what this means then is to enable PR environment? Or what exactly do you mean by having a staging environment.
Any pointers of how to do this will be gladly appreciated.
you can do either, pr environments and then run e2e tests on the services in that env, or a github branch for staging and a railway env for staging
thank you!