Question

A team uses AWS CodePipeline with a CodeCommit source, a CodeBuild build stage, and a CodeDeploy deploy stage. After a bad merge broke the latest commit, they want to re-run the pipeline against a specific earlier commit that they know is stable, without creating a new commit, reverting the branch, or modifying the pipeline definition. Which approach lets them execute the pipeline using that exact known-good commit?

Accepted Answer

Start a pipeline execution with a source revision override that specifies the desired commit ID for the CodeCommit source action.

Answer

Disable the CodeCommit source stage transition and manually upload the older commit's artifact to the pipeline's S3 artifact bucket.

Answer

Edit the pipeline to change the CodeCommit source action's branch to a temporary branch pointing at the older commit, then release the change.

Answer

Use the 'Retry stage' option on the failed deploy stage, which automatically pulls the last successful commit.