Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Mark build as "successful" even if it shows failed in AWS Elastic Beanstalk Pipe Integration

So I have a deployment step that has the following AWS Elastic Beanstalk pipe integration:

- pipe: atlassian/aws-elasticbeanstalk-deploy:1.0.2
variables:
AWS_ACCESS_KEY_ID: $AWS_DEPLOY_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_DEPLOY_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION
APPLICATION_NAME: $AWS_EB_APP_NAME
ENVIRONMENT_NAME: $AWS_EB_ENV_NAME
ZIP_FILE: "application.zip"
WAIT: "true"
DEBUG: "true"

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.

 

1 answer

0 votes
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 17, 2022

@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'

Regards, Igor

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events