- github의 origin main에 커밋한 내용을 push하면, Heroku가 이 내용을 감지하여 배포된 서버에 자동으로 반영해주는 기능이 있다.
- 하지만 제대로 반영되지 않은 커밋이 있어서, 다시 수정 후 커밋 후, git push heroku main 을 입력하여 해결하였다.
Heroku로 부터 아래 메일이 왔다!
An automatic deployment for nomadcoffee-backend-jiho failed. The build failed with the message Your account has reached its concurrent builds limit..
Token from user jiho1024@naver.com was used to interact with GitHub. This account was matched as the GitHub committer.
You can also check that the user who connected the app or pipeline to GitHub still has access to the app and to the Github repository.
In this case, reconnecting to GitHub will often fix the issue.
If you believe that this build failure was not due to an issue in your app, please open a support ticket.
-
즉 현재 빌드의 한계에 다다랐다는 내용인 것 같다. 이 내용을 구글에서 검색하였고, stackoverflow에 나와 유사한 케이스의 질문을 찾을 수 있었다.
https://stackoverflow.com/questions/47028871/heroku-your-account-has-reached-its-concurrent-build-limit -
그 중, 도움이 되었던 답변은 아래와 같다.
I had to try two of these answers back-to-back. Individually, they didn't work for me.
I needed to install heroku-builds with
heroku plugins:install heroku-buildsThen cancel the ongoing build with
heroku builds:cancelAnd finally did a heroku restart.
- 위 답변에 대한 댓글
This worked for me. Thanks. When you run heroku builds:cancel you may get the outout: Can only cancel pending builds. Build c20a59ad-d093-4c04-bc70-85ec62f1da00 has status 'failed', don't panic, just run the heroku restart command next, and the build will start. –
Promise Preston
Feb 12, 2021 at 15:57
