jkutner / graal-buildpack

MIT License
4 stars 6 forks source link

No longer seems to work on Heroku #4

Open sparkyspider opened 4 years ago

sparkyspider commented 4 years ago

Hi Joe,

I've been trying to deploy a Spring app on Heroku. It's crashing asking for JAVA_HOME. I've tried swapping the dependencies around as well as forking your buildpack to upgrade to lastest.

https://github.com/windflow-io/graal-buildpack

Hoping you can advise. When I left out the heroku/java it seemed to get further. I don't understand why the JAVA_HOME set by the script isn't sticking.

2020-10-01T20:07:19.263306+00:00 app[web.1]: 
2020-10-01T20:07:19.263361+00:00 app[web.1]: ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.
2020-10-01T20:07:19.263361+00:00 app[web.1]: 
2020-10-01T20:07:19.263362+00:00 app[web.1]: Please set the JAVA_HOME variable in your environment to match the
2020-10-01T20:07:19.263362+00:00 app[web.1]: location of your Java installation.
2020-10-01T20:07:19.263385+00:00 app[web.1]: 
2020-10-01T20:07:19.313318+00:00 heroku[web.1]: Process exited with status 1
2020-10-01T20:07:19.370346+00:00 heroku[web.1]: State changed from starting to crashed
2020-10-01T20:12:36.000000+00:00 app[api]: Build started by user mark@windflow.io
2020-10-01T20:12:49.000000+00:00 app[api]: Build failed -- check your build output: https://dashboard.heroku.com/apps/6f43cae9-7abf-42f6-882f-0090a0f6c0ee/activity/builds/f1d9ab86-a720-40b9-a8b7-00f918b52cd6
-----> GraalVM app detected
-----> Installing GraalVM
       - done
-----> Configuring
       - done
-----> App not compatible with buildpack: https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/java.tgz
       Could not find a pom.xml file! Please check that it exists and is committed to Git.
       More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
 !     Push failed

Help and advice appreciated.

sparkyspider commented 4 years ago

If I do the buildpack without heroku/java I seem to get much further...

Build

marks-local-machine:GraalVM sparkyspider$ git push heroku master --force Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 8 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 292 bytes | 292.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0) remote: Compressing source files... done. remote: Building source: remote: remote: -----> GraalVM app detected remote: -----> Installing GraalVM remote: - done remote: -----> Configuring remote: - done remote: -----> Discovering process types remote: Procfile declares types -> web remote: remote: -----> Compressing... remote: Done: 420.1M remote: -----> Launching... remote: ! Warning: Your slug size (420 MB) exceeds our soft limit (300 MB) which may affect boot time. remote: Released v5 remote: https://graalvm-test.herokuapp.com/ deployed to Heroku

Start App

2020-10-01T20:22:16.755172+00:00 heroku[web.1]: State changed from crashed to starting 2020-10-01T20:22:16.626143+00:00 app[web.1]: /app/.profile.d/graal.sh: line 1: 404:: command not found 2020-10-01T20:22:16.626162+00:00 app[web.1]: /app/.profile.d/jdbc.sh: line 1: 404:: command not found 2020-10-01T20:22:16.643893+00:00 app[web.1]: 2020-10-01T20:22:16.643896+00:00 app[web.1]: ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH. 2020-10-01T20:22:16.643896+00:00 app[web.1]: 2020-10-01T20:22:16.643897+00:00 app[web.1]: Please set the JAVA_HOME variable in your environment to match the 2020-10-01T20:22:16.643897+00:00 app[web.1]: location of your Java installation. 2020-10-01T20:22:16.643898+00:00 app[web.1]:

sparkyspider commented 4 years ago

https://graalvm-test.herokuapp.com/

sparkyspider commented 4 years ago

Adding a note that my use case is a gradle app with build.gradle (not pom.xml as per Maven) but that it was working before so not sure what changed on Heroku's side.

jorfermo commented 2 years ago

Same issue here