Deploy Aplikacji na serwer Heroku

0

Hej mam pytanie zrobiłam deploy aplikacji na serwer Heroku i pojawiają się błędy z którymi nie mogę sobie poradzić. Zmieniałam kilka rzeczy według wskazówek które były podane w internecie ale w dalszym ciągu nie działa. Może ktoś się orientuje co musiałabym zrobić. Z bazą się połączyłam i stworzyłam wszystkie tabele (ClearDB MySQL na heroku, połączenie na Workbench MySQL). Błędy na ekranie konsoli ->

2018-09-26T17:15:01.189907+00:00 heroku[web.1]: Starting process with command `java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port 36083 target/*.war`
2018-09-26T17:15:00.000000+00:00 app[api]: Build succeeded
2018-09-26T17:15:03.514146+00:00 heroku[web.1]: Process exited with status 1
2018-09-26T17:15:03.537161+00:00 heroku[web.1]: State changed from starting to crashed
2018-09-26T17:15:03.539517+00:00 heroku[web.1]: State changed from crashed to starting
2018-09-26T17:15:03.422059+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2018-09-26T17:15:03.423603+00:00 app[web.1]: Error: Unable to access jarfile target/dependency/webapp-runner.jar
2018-09-26T17:15:09.459973+00:00 heroku[web.1]: Starting process with command `java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port 54469 target/*.war`
2018-09-26T17:15:11.870026+00:00 heroku[web.1]: Process exited with status 1
2018-09-26T17:15:11.827404+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2018-09-26T17:15:11.828777+00:00 app[web.1]: Error: Unable to access jarfile target/dependency/webapp-runner.jar
2018-09-26T17:15:11.889672+00:00 heroku[web.1]: State changed from starting to crashed
2018-09-26T17:15:12.063455+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fierce-plains-35970.herokuapp.com request_id=17ef1801-7116-4313-a33a-517cdb18413a fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:15:12.631108+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fierce-plains-35970.herokuapp.com request_id=85fbf9d5-7ed0-469d-b5dc-f8a536d7dda7 fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:15:19.395636+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fierce-plains-35970.herokuapp.com request_id=202f54eb-cadb-4306-b4b2-a274b196736a fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:15:19.850556+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fierce-plains-35970.herokuapp.com request_id=b13b21b8-e9c4-4b0a-96be-510e2fce22d5 fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:17:05.000000+00:00 app[api]: Build started by user [email protected]
2018-09-26T17:17:31.351129+00:00 app[api]: Deploy 37db8721 by user [email protected]
2018-09-26T17:17:31.351129+00:00 app[api]: Release v10 created by user [email protected]
2018-09-26T17:17:32.131305+00:00 heroku[web.1]: State changed from crashed to starting
2018-09-26T17:17:37.082699+00:00 heroku[web.1]: Starting process with command `java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port 43757 target/*.war`
2018-09-26T17:17:36.000000+00:00 app[api]: Build succeeded
2018-09-26T17:17:39.197713+00:00 heroku[web.1]: Process exited with status 1
2018-09-26T17:17:39.248024+00:00 heroku[web.1]: State changed from starting to crashed
2018-09-26T17:17:39.128438+00:00 app[web.1]: Error: Unable to access jarfile target/dependency/webapp-runner.jar
2018-09-26T17:17:39.127008+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2018-09-26T17:18:07.094317+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fierce-plains-35970.herokuapp.com request_id=263cf747-318b-444c-a094-4e86f92e2cae fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:18:07.286646+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fierce-plains-35970.herokuapp.com request_id=db806356-3a7e-4a99-a78e-2ca6b6a94201 fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:25:09.810752+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fierce-plains-35970.herokuapp.com request_id=0a7e7c97-4c60-4b23-ae70-81b9e432fdc4 fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:25:09.630124+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fierce-plains-35970.herokuapp.com request_id=473a6bdc-8862-4118-b7e9-d839e0b8bef6 fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:30:37.886996+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fierce-plains-35970.herokuapp.com request_id=55dfbe87-6ea6-4e08-bd24-5641acaea951 fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https
2018-09-26T17:30:38.494622+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fierce-plains-35970.herokuapp.com request_id=53beb8d3-5cee-4706-b601-1eb1d0403314 fwd="91.231.27.214" dyno= connect= service= status=503 bytes= protocol=https

Plik Procfile

web: java $JAVA_OPTS -jar target/dependency/webapp-runner.jar --port $PORT target/*.war
0

Z tego nie bardzo cos widać. Podłącz się do konsoli przez CLI z terminala i może będzie stacktrace

0

Przypuszczalnie build nie utworzył katalogu dependency. Zaloguj się shelem do heroku i zobacz, czy jest tam ten katalog. Jak nie - puszczaj builda z poszerzonym logowaniem i obserwuj, co się dzieje.

Jak robiłem builda gradlem, to stworzył mi jara w jakimś z dziupli wyjętym katalogu, coś w stylu temp. Jak to zauważyłem, to dodałem do builda polecenia skopiowania tego jara. Efektem tych zmagań jest plik build.gradle, z odpowiednim celem stage.

1 użytkowników online, w tym zalogowanych: 0, gości: 1