a year ago
I have a monorepo and when I push no deployment happens. I don't know what could be wrong. I have manually deploy latest commit.
30 Replies
a year ago
Hello,
This could have been due to today's incident, can you confirm if this is still happening?
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Hello,This could have been due to today's incident, can you confirm if this is still happening?
a year ago
Still the same thing, I pushed again, no deployment was triggered
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Hello, I have exactly the same problem (Hobby plan). Can't deploy still, after 24hrs! Build is executed OK, but deployment fails.
a year ago
OK, it looks like that 24hrs ago something was change in the deployment process - it looks like I've need to change "Selected runtime" in Settings from "Legacy" to "V2". Error message was: "The selected runtime: LEGACY is not supported in this region".
aa
OK, it looks like that 24hrs ago something was change in the deployment process - it looks like I've need to change "Selected runtime" in Settings from "Legacy" to "V2". Error message was: "The selected runtime: LEGACY is not supported in this region".
a year ago
Yep you would need to switch to the V2 runtime.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
My changes aren't reflecting, can this be solved already I don't know what is going on
Status changed to Awaiting Railway Response Railway • about 1 year ago
Status changed to Awaiting User Response Railway • about 1 year ago
brody
You can switch to the V2 runtime in the service settings.
a year ago
I can't find the v2 runtime in the service settings
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Looks like you have since switched over to the V2 runtime! glad you got it resolved!
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved brody • about 1 year ago
Status changed to Awaiting Railway Response kelick-info • about 1 year ago
brody
Looks like you have since switched over to the V2 runtime! glad you got it resolved!
a year ago
I've been deploying manually, when I push to github it doesn't trigger any deployment. Look into this please
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
No it wasn't deployed from a template its a fresh project
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
What could be the issue why is deployment not triggering when I push to GitHub
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Yes and its only one branch I have which is main branch
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Can you try duplicating the service? right click and duplicate, does the duplicate service pick up the Git pushes?
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Can you try duplicating the service? right click and duplicate, does the duplicate service pick up the Git pushes?
a year ago
Okay I'm gonna try that and I'd let you know if it works or not
Status changed to Awaiting Railway Response Railway • about 1 year ago
kelick-info
Okay I'm gonna try that and I'd let you know if it works or not
a year ago
Didn't work, I duplicated the service and pushed to github no deployment was triggered. I'd be deleting the duplicate service now
brody
Can you try duplicating the service? right click and duplicate, does the duplicate service pick up the Git pushes?
a year ago
Didn't work, I duplicated the service and pushed to github no deployment was triggered. I'd be deleting the duplicate service now
brody
Long shot, I've removed your cached GitHub token, try pushing again.
a year ago
I've pushed severally and still not triggering, its surprising actually this is the first its has happened to me. And its a monorepo
a year ago
I'm not sure what to tell you here unfortunately, we don't have any other reports from users.
brody
I'm not sure what to tell you here unfortunately, we don't have any other reports from users.
a year ago
So how can it be resolved if I can't get automatic deployment when I commit to Github, I've tried everything disconnected Github created a new project and new service but same thing auto deployment is not triggering
Can you guys check what could be issue.
a year ago
We acknowledge the issue you are facing, but without providing reproducible steps that would allow us to reproduce it on our side, and without any other user reports, there is unfortunately nothing for us to look into here.
brody
We acknowledge the issue you are facing, but without providing reproducible steps that would allow us to reproduce it on our side, and without any other user reports, there is unfortunately nothing for us to look into here.
a year ago
I created a project -> created new service -> connected a github repo -> added the build & start command and env-> selected singapore as region -> deploy
Then when I push it doesn't auto deploy I have to trigger a deployment manual using cmd+k "deploy latest commit"
Can y'all see my github pushes or commits, maybe you guys should see why its not triggering build
a year ago
GitHub based builds are triggered when GitHub sends a webhook, if they aren't sending us a webhook then there's not all that much we can do as we don't have any viability into GitHub's systems, furthermore, we have zero user reports of this issue.
We just don't have the cycles to look into one-off unreproducible reports at this time, unfortunately.
brody
GitHub based builds are triggered when GitHub sends a webhook, if they aren't sending us a webhook then there's not all that much we can do as we don't have any viability into GitHub's systems, furthermore, we have zero user reports of this issue.We just don't have the cycles to look into one-off unreproducible reports at this time, unfortunately.
a year ago
So in general what you're saying is, this is something you guys can't debug or figure out what could be wrong?
a year ago
Its not that we can't its that we don't have the cycles to debug one-off reports that are unreproducible at this time.
If you were able to provide reproducible steps or if there where more user reports of this issue, we would be able to spare cyles to look into this.
brody
Its not that we can't its that we don't have the cycles to debug one-off reports that are unreproducible at this time.If you were able to provide reproducible steps or if there where more user reports of this issue, we would be able to spare cyles to look into this.
a year ago
No problem i'd be deploying manually for the meantime. You can close this thread
a year ago
Will do, please open a new thread if you come across reproducible steps, they will be much appreciated.
Status changed to Closed brody • about 1 year ago
