8 months ago
I am having issues with deployment of my service in both environments of the project.
Project
172feb9c-0b70-40a7-ac13-33f01f663c5e
Service
26a0d025-6f7e-4dba-b967-24ecd0a6ab9a
The problem is, when I deploy this manually, by changing an environment variable or something else, it works great, deploys fine, uses the configured railway.json.
But when I try to commit to /develop the branch and folder for that this service's watch, for some reason, the job to build immediatly returns, with the "REMOVED" tag, it uses a railway.json file that is not configured, and it marks the run as failed in Github.
Am I doing something wrong here? I have tried recreating the service, and then this issue will migrate to a different service.
5 Replies
To add, in the ghost deployment, falling back to NIXPACKS when this is a dockerfile deployment as configured in the railway.json, and if I look at that REMOVED deployment that was canceled before it even began, it gives me the prompt "Save this in a file called railway.json to codify your deployments config.", when that is already specified for the service, which I know because it works fine if I manually trigger the build.
8 months ago
do you think you could get a screen recording of this issue?
Guess I cried wolf, this was doing what I described earlier today and the past few days, but its not now.
I did upgrade to the Hobby plan so maybe it was something with Trial credits? Either way Ill keep a link to this thread if it pops up again but its solved now
8 months ago
no problem!