5 years ago
When setting up automatic deploys on push, add an option to wait for status checks to pass on the repository before deploying.
7 Replies
Status changed to Planned jake • over 4 years ago
4 years ago
Does the new Healthchecks feature solve your use-case? https://docs.railway.app/diagnose/healthchecks
Status changed to In Progress angelo-railway • about 4 years ago
4 years ago
Healthchecks should solve this usecase. For more information see: https://docs.railway.app/diagnose/healthchecks
Status changed to Completed angelo-railway • almost 4 years ago
4 years ago
Healthchecks doesn't solve this. This is about waiting for a successful CI build, the application should never be deployed until the CI passes. Just because a healthcheck passes and the server is responding, doesn't mean all of the unit tests passed.
Status changed to Planned jake • almost 4 years ago
3 years ago
Healthchecks doesn't solve this. This is about waiting for a successful CI build, the application should never be deployed until the CI passes. Just because a healthcheck passes and the server is responding, doesn't mean all of the unit tests passed.
Oden: Gotcha, we just considered this feature but I think we are a little light on requirements.
Do you need us to talk to an external CI provider? Or would you want something like native support for GitHub Actions out of the box.
3 years ago
Healthchecks doesn't solve this. This is about waiting for a successful CI build, the application should never be deployed until the CI passes. Just because a healthcheck passes and the server is responding, doesn't mean all of the unit tests passed.
Angelo Saraceno: Ideally it would just integrate with GitHub's Checks API, and only deploy after they have all passed on the commit. That way it would work with any CI/testing provider that is set up for the repository.
3 years ago
This is the same as Heroku's "Wait for CI to pass before deploy” checkbox." https://devcenter.heroku.com/articles/github-integration#automatic-deploys
3 years ago
Hey y'all, this feature is now available to our beta users. We'd love some feedback on how to improve it.
You can read more about it in our docs: https://docs.railway.app/deploy/deployments#check-suites
Status changed to In Progress fp • about 3 years ago
3 years ago
we solved this by having a separate branch/repo into which CI pushes latest after successful build
2 years ago
This has been deployed for a while
Settings -> Wait for CI
Status changed to Completed jake • over 2 years ago
4 months ago
I use the Settings -> Wait for CI toggle in the UI. Is this setting this configurable in railway.json ? I do not see it in the docs, or the schema.
For context, I'd like to programmatically toggle it ON for existing previews. By way of experimentation, it appears that the setting is durable for new Preview deployments but not existing Previews.
i.e. toggling it to ON for the master deployment will result in subsequent Preview deployments also having it toggled ON, but re-deployments of existing Previews will continue to have it turned OFF . Is this correct?