Open oleksii-mykhniak opened 2 years ago
Here is a quick and dirty workaround.
Add gem install faraday -v 1.8.0
before running dpl --provider=heroku --app=$APP --api-key=$HEROKU_API_KEY
.
It ain't pretty, but DEV's got to deploy.
It looks like the change affected was https://github.com/lostisland/faraday/pull/1354
This is my update for Gitlab CI, works perfectly with Faraday 1.8.0
deploy:
stage: deploy
only:
- master
image: ruby:latest
script:
- gem install dpl && gem install faraday -v 1.8.0
- dpl --provider=heroku --app=xxx --api-key=$HEROKU_API_KEY
https://github.com/lostisland/faraday/issues/1362#issuecomment-1006958547 says that Faraday 2.0.1 reverted/fixed the change that made Faraday 2.0.0 not work but I put up #1249 just in case that doesn't work or it changes, so that someone who is maintaining dpl
can qualify dpl
against Faraday 2.x properly.
I faced the same problem today. Apparently there is some problem in the latest version of FARADAY, at the moment. I solved it this way: add manual installation of the previous version of the dependency to your .gitlab.yml, and everything will work. Have a nice day.
before_script:
- apt-get update -qy
- apt-get install -y ruby-dev
- gem install dpl
- gem install faraday -v 1.8.0
I'm using dpl in GitLab for Heroku CI/CD and I have the next error:
It looks like a problem in the faraday-2.0.0 release which was a few minutes ago here