Question

A development team uses AWS CodePipeline with a source stage connected to a GitHub (via CodeStar Connections) repository. Developers complain that after they push commits, the pipeline sometimes takes several minutes to start. The team wants pipeline executions to begin as quickly as possible after each push while minimizing unnecessary source checks. Which configuration best achieves this?

Accepted Answer

Enable webhook-based change detection so that GitHub push events trigger the pipeline immediately through the CodeStar connection.

Answer

Configure CodePipeline periodic polling with the shortest allowed interval to detect new commits faster.

Answer

Add an EventBridge scheduled rule that runs every minute to invoke the StartPipelineExecution API.

Answer

Enable full clone in the CodeBuild source configuration to reduce the delay before the pipeline starts.