You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
So I have a deployment step that has the following AWS Elastic Beanstalk pipe integration:
- pipe: atlassian/aws-elasticbeanstalk-deploy:1.0.2
Sometimes the build will notify me of failure due to the environment's health being red, but in reality the build was successful deployed in the environment. When I try to manually re-run the deployment step, it will fail saying that the particular version is already uploaded (An error occurred (InvalidParameterValue) when calling the CreateApplicationVersion operation: Application Version aws-eb-app-name-472-11e2152e already exists.).
So what I'm trying to do is either manually mark the build as "successful" or a way to have the deployment step re-run without encountering the upload error.
@Marl Bermudo hi. Thanks for your question.
Try to use WARMUP_INTERVAL (warmup time for some of customer edgecases) variable.
- pipe: atlassian/aws-elasticbeanstalk-deploy:1.0.2 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION APPLICATION_NAME: 'application-test' COMMAND: 'deploy-only' VERSION_LABEL: 'deploy-$BITBUCKET_BUILD_NUMBER-multiple' ENVIRONMENT_NAME: 'production' WAIT_INTERVAL: 60 WARMUP_INTERVAL: 30 WAIT: 'true'