Question

A team uses AWS CodePipeline with a Source stage (CodeCommit), a Build stage (CodeBuild), a manual approval action, and a Deploy stage. Developers frequently push multiple commits in quick succession. They notice that when several executions are queued, an older execution sometimes reaches the manual approval gate and gets approved and deployed AFTER a newer commit has already been deployed, causing an older version of the code to overwrite the newer one in production. The team wants to guarantee that only the most recent change is deployed and that superseded executions are not deployed. What is the MOST appropriate solution?

Accepted Answer

Enable the pipeline's default SUPERSEDED execution mode so that when a newer execution enters a stage, it replaces the older waiting execution, ensuring only the latest change advances.

Answer

Switch the pipeline to PARALLEL execution mode so each commit runs independently and cannot interfere with other executions.

Answer

Add a Lambda function before the Deploy stage that compares commit timestamps and aborts the pipeline if a newer commit exists.

Answer

Configure the manual approval action with a short timeout so stale approvals expire before they can be actioned.