Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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.

 

1 answer

1 accepted

0 votes
Answer accepted

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. 

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.

Like # people like this

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

190 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you