0

For some reason AWS Codedeploy rollback seems to always pick up the latest version and fails

Deployment 1 is success and a revision is created in S3 bucket.

Deployment 2 is failure and Codedeploy rollback kicks in which is Automatic

Deployment 3 also fails for the same reason as Deployment 2

Expected Codedeploy behaviour is for Deployment 3 it should pick up the Deployment 1 S3 build version.

I am not sure if there are any missing links in S3 bucket with Codedeploy. Any thoughts much appreciated.

Thank you

sakworld
  • 77
  • 5

2 Answers2

0

Not sure if this applies to your situation specifically, but "strange" rollback behavior of CodeDeploy is documented:

However, if the deployment that failed was configured to overwrite, instead of retain files, an unexpected result can occur during the rollback.

Thus it is possible that you are observing these "unexpected results" that can occur when you deploy and fail with an existing content.

You can read up more on that in:

Marcin
  • 215,873
  • 14
  • 235
  • 294
0

After a bit of investigation with AWS CLI, I can see the the version being re written. Things are more clear when using the AWS CLI than what is shown in the console.

Thank you for taking the time to post back with a possible answer

sakworld
  • 77
  • 5