Why GitHub commit deployment
Why GitHub commit deployment doesn't override the current active deployment done from the railway CLI (railway up), the new commit build & deployment just hangs on "Waiting" state, and won't be built nor deployed, is this intentional or am I doing something wrong?
17 Replies
Project ID:
72410772-42cf-43c4-b589-92bfb7b38c8b72410772-42cf-43c4-b589-92bfb7b38c8b
Service 842b8e6a-0a1e-443c-ba13-d0b450e2b465
that doesn't seem right
Uhh anyone know why this happened
It's probably an internal issue, maybe GCP is causing deployments to be delayed again
Yeah it might be GCP
Can you check the deploy logs ("view logs" button in the latest deploy)? It probably has more information there
The core team will be at the desk in about 4 hours, until then we can only try to figure it out with your help
There’s no deploy logs
No deploy or build logs
We had similar issues in the last few days and it was caused by the GCP
Issues like this is the main reason why Railway is moving away from them
All we can do for now is wait until the team rolls out a fix
I thought gcp is generally reliable
It is, Google just treats their customers as crap
do you have wait for ci enabled or something like that?
Yeah but there’s nothing that can block it
Because there’s no other action running other then railway
Although I can try switching it off
And there’s no way a CI action can run for a day
maybe the ci failed? (if so the deployment should reflect that, but still check)