Builds suddenly fail with "Error installing dpl"

Deployment
1

It seems all my builds suddenly started to fail:

$ rvm $(travis_internal_ruby) --fuzzy do ruby -S gem uninstall -aIx dpl Gem 'dpl' is not installed 30.39s$ rvm $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl --pre ERROR: Error installing dpl: The last version of dpl (>= 0) to support your Ruby & RubyGems was 2.0.3.beta.4. Try installing it with gem install dpl -v 2.0.3.beta.4 dpl requires Ruby version >= 3. The current ruby version is 2.7.6.219. Successfully installed mime-0.4.4 Successfully installed json_pure-2.7.2 Successfully installed excon-0.110.0 Successfully installed travis-packagecloud-ruby-1.1.0 Successfully installed regstry-1.0.15 Successfully installed travis-cl-1.2.4 The command "rvm $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl --pre" failed and exited with 1 during .

3 Likes
2

BUMP. We have the same issue.

$ rvm $(travis_internal_ruby) --fuzzy do ruby -S gem uninstall -aIx dpl
Gem 'dpl' is not installed
32.03s$ rvm $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl --pre
ERROR:  Error installing dpl:
	The last version of dpl (>= 0) to support your Ruby & RubyGems was 2.0.3.beta.4. Try installing it with `gem install dpl -v 2.0.3.beta.4`
	dpl requires Ruby version >= 3. The current ruby version is 2.7.6.219.
Successfully installed mime-0.4.4
Successfully installed json_pure-2.7.2
Successfully installed excon-0.110.0
Successfully installed travis-packagecloud-ruby-1.1.0
Successfully installed regstry-1.0.15
Successfully installed travis-cl-1.2.4
The command "rvm $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl --pre" failed and exited with 1 during .

This build was working fine this morning.

EDIT: Seem that the dpl gem was updated today: Release v2.0.3-beta.5 · travis-ci/dpl · GitHub

3 Likes
3

BUMP. Same issue on our side, multiple builds failing with the same error.

As you said, seems to have something to do with the new dpl beta release.

2 Likes
4

BUMP. Same issue here, kept restarting but nothing changed. Here to see if a fix is released.

1 Like
5

We saw the same issue in our builds. From what I can see, the version of ruby that is pointed to in the “$(travis_internal_ruby)” variable is locked to a version to support their build scripts. This looks to have caused an issue with the latest release of dpl requiring a higher ruby version.
Short term, we are using the following option in our .travis.yml file to “lock” the dpl version to the previous release until a fix is found. Just wanted to share in case it can help others as all of our deploys were erroring until adding the branch option. This may break later, but it works now for us.
I am providing the partial block out of context and we use the script provider, so please adjust to fit your needs. Prior, we just had “edge: true”.

      deploy:
        provider: script
        edge:
          branch: v2.0.3-beta.4
7 Likes
6

^ Thanks it worked for us

7

This worked for us . Thank you.

8

branch: v2.0.3-beta.4 stopped working for me, using branch: v2.0.5-beta instead