CODEWITHSUNDEEP
dockerheroku
Shamnad P S
Shamnad P S

Reputation: 1173

Heroku deploy is stuck using heroku.yml

I am using Heroku auto-deployment using the heroku.yml file.

And the release step seems to be running forever and it's not failing or succeeding.

Could anyone help what I am doing wrong?

Below are the contents of the heroku.yml file.

build:
  docker:
    web: Dockerfile
release:
  image: web

Its been running for more than 20 min now,

enter image description here

Heroku logs seems fine

2018-09-17T16:29:17.000000+00:00 app[api]: Build started by user [email protected]
2018-09-17T16:32:11.000000+00:00 app[api]: Build succeeded
2018-09-17T16:32:11.463973+00:00 app[api]: Deployed web (8711c8889299), release (8711c8889299) by user [email protected]
2018-09-17T16:32:11.463973+00:00 app[api]: Running release v8 commands by user [email protected]
2018-09-17T16:32:12.484201+00:00 app[api]: Starting process with command `if curl $HEROKU_RELEASE_LOG_STREAM --silent --connect-timeout 10 --retry 3 --retry-delay 1 >/tmp/log-stream; then
2018-09-17T16:32:12.484201+00:00 app[api]: /tmp/log-stream /bin/sh -c 'npm start'
2018-09-17T16:32:12.484201+00:00 app[api]: else
2018-09-17T16:32:12.484201+00:00 app[api]: chmod u+x /tmp/log-stream
2018-09-17T16:32:12.484201+00:00 app[api]: npm start
2018-09-17T16:32:12.484201+00:00 app[api]: fi` by user [email protected]
2018-09-17T16:32:26.348412+00:00 heroku[release.7596]: Starting process with command `if curl https://heroku-release-output.s3.amazonaws.com/log-stream?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=1234%2F20180917%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180917T163211Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=1234 --silent --connect-timeout 10 --retry 3 --retry-delay 1 >/tmp/log-stream; then   chmod u+x /tmp/log-stream   /tmp/log-stream /bin/sh -c 'npm start' else   npm start fi`
2018-09-17T16:32:26.941800+00:00 heroku[release.7596]: State changed from starting to up
2018-09-17T16:32:28.128927+00:00 app[release.7596]: /bin/sh: curl: not found
2018-09-17T16:32:28.615282+00:00 app[release.7596]:
2018-09-17T16:32:28.615322+00:00 app[release.7596]: > [email protected] start /backend
2018-09-17T16:32:28.615324+00:00 app[release.7596]: > ts-node -r tsconfig-paths/register src/main.ts
2018-09-17T16:32:28.615326+00:00 app[release.7596]:
2018-09-17T16:32:30.751179+00:00 app[release.7596]: [Nest] 27   - 9/17/2018, 4:32:30 PM   [NestFactory] Starting Nest application...
2018-09-17T16:32:30.763686+00:00 app[release.7596]: [Nest] 27   - 9/17/2018, 4:32:30 PM   [InstanceLoader] AppModule dependencies initialized +12ms
2018-09-17T16:32:30.815330+00:00 app[release.7596]: [Nest] 27   - 9/17/2018, 4:32:30 PM   [RoutesResolver] AppController {/}: +52ms
2018-09-17T16:32:30.819278+00:00 app[release.7596]: [Nest] 27   - 9/17/2018, 4:32:30 PM   [RouterExplorer] Mapped {/, GET} route +4ms
2018-09-17T16:32:30.821509+00:00 app[release.7596]: [Nest] 27   - 9/17/2018, 4:32:30 PM   [NestApplication] Nest application successfully started +2ms

Upvotes: 3

Views: 2069

Answers (1)

Shamnad P S
Shamnad P S

Reputation: 1173

So the solution was to add something as release command. its weird enough but works fine. Let me know if this works for anyone.

build:
  docker:
    web: Dockerfile
release:
  image: web
  command:
    - echo 'Starting server after deployment!';

Upvotes: 3

Related Questions