Closed
Description
Found in #43938
�[0Ktravis_fold:end:dpl.0
�[0Ktravis_time:start:0914d468
�[0Ktravis_fold:start:dpl.1
�[33mInstalling deploy dependencies�[0m
ERROR: Could not find a valid gem 'aws-sdk-core' (= 2.10.35) in any repository
ERROR: Possible alternatives: aws-sdk-core
/home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- aws-sdk (LoadError)
from /home/travis/.rvm/rubies/ruby-2.2.7/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:85:in `requires'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:6:in `<class:S3>'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:5:in `<class:Provider>'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:4:in `<module:DPL>'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider/s3.rb:3:in `<top (required)>'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:59:in `const_get'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:59:in `block in new'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/cli.rb:41:in `fold'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/provider.rb:56:in `new'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/cli.rb:31:in `run'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/lib/dpl/cli.rb:7:in `run'
from /home/travis/.rvm/gems/ruby-2.2.7/gems/dpl-1.8.40/bin/dpl:5:in `<top (required)>'
from /home/travis/.rvm/gems/ruby-2.2.7/bin/dpl:22:in `load'
from /home/travis/.rvm/gems/ruby-2.2.7/bin/dpl:22:in `<main>'
travis_fold:end:dpl.1
failed to deploy
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
kennytm commentedon Aug 29, 2017
The error means the gem repository is not up-to-date, and a retry will usually fix it. This happened at least twice before:
Maybe we could do something like
gem update
before deploying to S3.19 remaining items