Error: Unsupported Gradle version: 8
==============
Using Nixpacks
==============
context: 78ee202a04734b630f61d71bea3f81cd
Nixpacks build failed
Using Gradle-8.2.1
Trying to build native image and run
17 Replies
Project ID:
5113fced-71fc-4685-8a11-17cc8e69bbbbservice id 5113fced-71fc-4685-8a11-17cc8e69bbbb
railway only supports up to grade 7
i have downgraded but still deployment is failing.
Source contains h2 in-memory database and simple spring boot application
sorry I'm not a java developer, all I knew is that railway didn't support gradle 8
understood.
however i have downgraded to gradle 7. same application runs in local which fails for deplpoyment
wanted to try out railway
i can't see complete error reason as the logs being stored to file: /root/.gradle/daemon/7.5.1/daemon-39.out.log
may i know how can i extract failure logs which doesn't show in deploy logs console
Also may i know 5$ credit will be an reoccurring one (trial account)?
you can't access files on the container of it's not through your app
on the trial account, you will only get the 5$ once
ok
how can i see complete error which is causing failure
whom can help on this.
I can see it't running locally fine and in a docker image as well
again I'm not a java developer, I'm only here because there is a few question I have been able to answer
only in railway app it's not deploying
yes you have said that multiple times
you'll have to wait for someone to come around who is a java developer
alright, will someone be pointed to this conversation.
thank you for your response
this is a public thread in the server, open to anyone to come in and help
have a good day.
This is pretty old but just in case... Spring started up so most likely your app crashed because it failed to connect to the JPA Repo.
the not so helpful hint is in this last logged line "RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 539 ms. Found 1 JPA repository interfaces." It found a repo but probably failed to conenct causing it to crash. Not sure where the follow up logging went.. some sort of stack dump should have followed but I'd bet on a connection issue.