5 months ago
Hey! Just noticed that when preDeployCommand fails (in this case I am running db migrations) I am not getting an error log as to what error occurred in the console. This is a big issue currently as we can't figure out whats causing the failure when build is succeeding and currently cant deploy the updates.
14 Replies
5 months ago
Link to the service in question, please.
Sorry Brody didn't see this last night! Service in question: https://railway.com/project/55241924-4c30-497d-b496-165a1ec58a56/service/13663ec4-f514-46bf-8ca1-1395a4134e5b/settings?environmentId=629efb80-744b-4e5a-864b-ca28ed0b796a
5 months ago
I see deploy logs?
Are you looking at the successful or failed @Brody ? https://railway.com/project/55241924-4c30-497d-b496-165a1ec58a56/service/13663ec4-f514-46bf-8ca1-1395a4134e5b?environmentId=629efb80-744b-4e5a-864b-ca28ed0b796a&id=5723ece7-1d09-47ae-950c-28c956237540#build should show "Predeploy command failed"
Confirmed it isn't a schema issue, as I was able to manually apply the migration
5 months ago
You can click through to the deploy logs to see the logs for the failed pre-deploy command.
5 months ago
Since there isn't anything sensitive, here are the logs.
5 months ago
If there is no stack trace, the application didn't print one. You would have to turn on verbose logging, but I'm not sure how you would do that with Drizzle.