Open mattsrobot opened 1 year ago
Thanks for the bug report! I suspect that builds are timing out. Properly caching the gems between builds should help quite a bit.
@mattsrobot have a look in here for a way to cache ruby builds https://github.com/railwayapp/nixpacks/pull/817#issuecomment-1475032321
Is there an existing issue for this?
Describe the bug
Dear Railway team,
I've noticed occasionally, using a Ruby nixpacks project, builds can fail at a certain step, and cause Railway to rebuild the project for quite a long time (typically 30 minutes unless manually cancelled).
The particular step is this line:
Resulting with an error, deadline exceeded:
One note additionally,
I've noticed gems don't seemed to be cached between builds, is it possible to add some sort of cache between builds? The longest part of building the project seems to be related to gem installation. Typical build time is around 10 minutes.
To reproduce
any ruby project (3.2.2) - intermittent failure.
Expected behavior
Should install
Environment
Production