a month ago
Three consecutive CLI deployments fail before executing any build step.
Project: pulso-operativo-ia
Project ID: f4ddb069-2a6e-48c9-9e57-57746445c8d2
Service ID: ff96aeef-5832-400e-ac68-2599548470ff
Environment: production
Environment ID: 96a02d76-bbaf-41d7-8a3a-f40882871edb
Region: us-east4-eqdc4a
CLI version: 5.27.2
Configuration: Railpack / buildEnvironment V3
Builder assigned: builder-uejfcx
Failed deployment IDs:
- 740edcd9-6535-4aed-b6a6-40f590210a16
- 88668d03-190a-4100-913c-a625b07bc420
- 8f27ed6b-d53f-4d92-8b89-f998d6819f76
Every deployment only produces these lines:
scheduling build on Metal builder "builder-uejfcx"
scheduling build on Metal builder "builder-uejfcx"
The source is indexed, compressed and uploaded successfully. No install,
Railpack, application build, migration or deployment logs are produced.
The application builds successfully locally. TypeScript, lint and 24 tests
also pass. We upgraded Railway CLI, waited 15 minutes and performed a fresh
railway up, but the same builder failed again.
The Metal Build Environment toggle is no longer available in the service UI,
and buildEnvironment is no longer editable through ServiceInstanceUpdateInput.
Related Railway report with the identical infrastructure failure:
https://station.railway.com/questions/all-builds-fail-instantly-on-metal-build-3aadfff8
The suggested NO_CACHE=1 workaround and a fresh railway up did not resolve
the issue there. Our deployment also fails before any cache or build step.
Please reassign builder-uejfcx to a healthy builder.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your builds are actually reaching the builder and running, they're failing inside the build itself: npm ci is exiting with code 1 about 2 seconds in. That error should have shown up in your build logs and didn't, which made it look like the builder was broken. Sorry about that, we're looking at the log gap on our side.
An npm ci failure that fast usually means package-lock.json isn't in the uploaded source. Since you're deploying with railway up, check that the lockfile isn't excluded by .gitignore or .railwayignore. If it's there, try running npm ci in a clean clone of exactly what you upload.
Railway Team
Status changed to Awaiting User Response Railway • about 1 month ago
23 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 23 days ago