2.1.1.2. Version Control Integration with Pipelines
2.1.1.2. Version Control Integration with Pipelines
Loading diagram...
The connection between version control and your pipeline determines how fast your team gets feedback. A poorly configured trigger means developers wait minutes (or hours) for builds that should start in seconds.
Trigger mechanisms vary by source provider. CodeCommit repositories trigger pipelines via EventBridge rules that detect referenceCreated or referenceUpdated events. GitHub connections use webhooks via AWS CodeStar Connections (now CodeConnections). S3 sources require CloudTrail logging on the bucket ā without it, polling is the only option (slow and costly).
Branch strategies for pipelines: a common pattern uses main for production, develop for staging, and feature branches for development. CodePipeline can be configured with multiple pipelines per repository ā one triggered by main (deploys to prod) and another by develop (deploys to staging). Alternatively, use a single pipeline with a manual approval action before the production deploy stage.
Exam Trap: CodePipeline doesn't natively support triggering on specific branch patterns. If you need branch-based routing (e.g., only release/* branches trigger production), you must use EventBridge rules with content filtering on the branch name, then use the event to start the appropriate pipeline.
š” Tip: Always disable PollForSourceChanges when using event-based triggers. Polling adds latency and costs API calls against your source provider.
