You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This code doesnt work with Jenkins2.0 because of aws-sdk issue
It doesnt work from jenkins 2.46.3.
ruby /usr/share/tomcat6/scripts/aws/sqs_send_message.rb Deployment 34.208.27.13
/usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in require': cannot load such file -- aws-sdk-v1 (LoadError) from /usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in require'
from /usr/share/tomcat6/scripts/aws/sqs_send_message.rb:2:in `'
Build step 'Execute shell' marked build as failure
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE
The text was updated successfully, but these errors were encountered:
Can you atleast know the rubygems version used along with the aws-sdk-v1 so that I will install that and try it again? I guess with aws-sdk requires rubygems 2.0. so it is not working. Its tedious to convert all the API's of aws-sdk-v1 to aws-sdk format.
sonijenk
changed the title
code have dependencies with aws-sdk version i guess.
ruby gems version used with aws-sdk-v1(I used 1.67.0) but ruby gems is 2.0 and still fails
May 29, 2017
This code doesnt work with Jenkins2.0 because of aws-sdk issue
It doesnt work from jenkins 2.46.3.
/usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in
require': cannot load such file -- aws-sdk-v1 (LoadError) from /usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:55:in
require'from /usr/share/tomcat6/scripts/aws/sqs_send_message.rb:2:in `'
Build step 'Execute shell' marked build as failure
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE
The text was updated successfully, but these errors were encountered: