Use railway logs -b (or railway logs --build) to view build logs from the CLI. Make sure you have a project linked first with railway link. If you have multiple services, you may also need to run railway service to select which one you want logs from.

Hi, attached is a side by side comparison between what I get from the log command you provided and what I get from the interface.

What i get from the interface is useful and point to the issues, what I get from the command line is rather useless.

Please help.

Thanks

Can you describe what's different? Are your referring to the error?

I have a hard thinking that a 2 images were not worth 2000 words but, here we go:
- in the interface you clearly have an error (see error in RED). This helps pin point what to fix.
- in the log you have no error. This means I still have to log in to the interface to understand what went wrong. This defeats the purpose of a CLI

In your screenshot, the build done with the CLI was successful, so there are no errors to return. In the UI, that build failed, so there are errors to show.

No, no, no. That is the problem. Otherwise I would not be filing a ticket. it was not succesful but I was not getting any errors from the CLI build logs. Actually most of the time I wonder what is the relation between the cli build log and the one I see in the interface. So I assume I must be missing something. That something is absolutely NOT, showing build logs for 2 different situation as a way of demonstrating a descrepancy. That would be incredibly absurd. I hope this clears things up. It very frustrating to wait for 3 days to such an answer.

Took me a bit... and sorry for the incredulousness but I have a fix for you: https://github.com/railwayapp/cli/pull/782

After merge, it should resolve the issue.