Source retrieval, build, test, and deployment should run in sequence when a change occurs.
Connect the stages into a pipeline.
Which service is most appropriate?
AWS CodePipeline automates and connects source, build, test, and deployment stages.
Detailed explanation
CodePipeline coordinates source, build, test, and deployment actions in a workflow.
CodePipeline coordinates source, build, test, and deployment actions in a workflow.
X-Ray traces distributed application requests.
X-Ray traces distributed application requests.
CodeBuild executes builds but does not orchestrate every pipeline stage by itself.
CodeBuild executes builds but does not orchestrate every pipeline stage by itself.
AppStream streams desktop applications to users.
AppStream streams desktop applications to users.
Check official documentation
Compare the following points with the official documentation.
AWS CodePipelineの公式概要でステージとアクションの連携を確認する。
Official references
What to confirm
CI/CD工程の自動連携へCodePipelineを選べる。
Key points
- CodePipeline
- Stage
- CI/CD
Notes
- Environment:
- AWS service features and names can change; confirm current behavior in the official AWS documentation.
Foundation review
Choose by purpose
A notification, queue, support case, build stage, desktop, browser, frontend, and IoT device have different service boundaries.
Separate adjacent services
Services may work together, but the question asks which one owns the required capability.