Closed avatsaev closed 7 years ago
a similar error
Jenkins v.2.3.0 AWS Elastic Beanstalk Deployment Plugin v.0.3.10 Amazon Web Services SDK v.1.11.37 Token Macro Plugin v.2.0
Am also stucked here :(
+1
for everyone having this issue, (and ingenieux completely ignoring us) the workaround is to disable rolling updates by unchecking it in the config
Vatsaev,
Im not ignoring. Just the usual answer: patches welcome
Now be nice and i wont tell santa about this ok?
On Dec 14, 2016 16:45, "Vatsaev Aslan" notifications@github.com wrote:
for everyone having this issue, (and ingenieux completely ignoring us) the workaround is to disable rolling updates by unchecking it in the config
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ingenieux/awseb-deployment-plugin/issues/47#issuecomment-267166342, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPctYzZE_5drcUUYR9qAWPFmXrMfqMNks5rIGNhgaJpZM4KMDu9 .
joke's on you, santa isn't real.
I'm really trying to understand why this is happening, but I suck at java, pinpointed the issue to file ZeroDowntime.java at line 142, seems like whatever getAwseb() is returning, it doesn't have the swapEnvironmentCNAMEs() method, where is getAwseb() coming from? and what is it returning?
It might be a breaking change in the aws sdk for java. It used to work on older versions
On Dec 15, 2016 01:26, "Vatsaev Aslan" notifications@github.com wrote:
I'm really trying to understand why this is happening, but I suck at java, pinpointed the issue to file ZeroDowntime.java at line 142, seems like whatever getAwseb() is returning, it doesn't have the swapEnvironmentCNAMEs() method, where is getAwseb() coming from? and what is it returning?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ingenieux/awseb-deployment-plugin/issues/47#issuecomment-267229025, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPctUuzxn_TeCPxcMsGlqLJ6iL0jsn0ks5rILN9gaJpZM4KMDu9 .
You can't lock on to an older version of the SDK? Like Gemfile.lock that locks major versions of Gems on Ruby projects to prevent this sort of issues. Not sure how package management works on Java.
Anyway, bumped to a newer version of aws-sdk and deployed. Give it a try.
Here is the trace: