EB deployment doesn't fail the pipeline when version is not deployed

[Anton Roslov]

We are using the atlassian/aws-elasticbeanstalk-deploy:0.2.5 pipe

When deploying EB actually fails to roll out the new version. This can be seen in Pipeline execution log:

INFO: Deploying to environment "backend-prod". Previous version: "Backend-7726-65a956a5" -> New version: "Backend-7756-0420f451".
:heavy_check_mark: Deployment triggered successfully. URL: http://masked.ap-southeast-1.elasticbeanstalk.com
...
INFO: Checking deployment status in Elastic Beanstalk...
INFO: Environment "backend-prod" is now running version "Backend-7726-65a956a5" with status "Ready".

you can see that the new version is actually not deployed, and old version is still running, however pipeline never fails and incorrectly marks deployment as completed in Bitbucket, thus making the notifications and Deployments dashboard useless.

[Alexander Zhukov · Accepted solution]

Hi Anton,
It turns out, there is a minor bug in the pipe. It looks like the output says that the old version is running, while the new version is actually deployed. Basically, your deployment is ok and you should be able to verify that the new version was actually deployed to Elasticbeanstalk using AWS console. 

[Alexander Zhukov]

Actually, it looks like the bug was different. Indeed, the deployment might go wrong and rollback to the older version, which wasn't handled in the pipe correctly. We're already fixing the bug.

[Alexander Zhukov]

FYI, the bug was fixed in the 0.2.8 version of the pipe.