Notes
- CodePipeline을 생성하면 자동으로 중간 데이터 저장용 s3 버킷 생성된다.
- 버킷명 예: codepipeline-region-1234567EXAMPLE
- If a pipeline contains multiple source actions, all of them will be run again, even if a change is detected for one source action only
- A stage can only process one revision at a time. A revision must run through a stage before the next revision can run through it.
- When a stage is complete, by default the revision will transition to the next stage in the pipeline. You can disable a transition from one stage to the next. When you do, your pipeline will run all actions in the stages before that transition, but will not run any stages or actions after that stage until you enable that transition. This is a simple way to prevent changes from running through the entire pipeline. After you enable the transition, the most recent revision that ran successfully through the previous stages will be run through the stages after that transition. If all transitions are enabled, the pipeline runs continuously; every revision will be deployed as part of a successful run through the pipeline (continuous deployment).
- An approval action prevents a pipeline from transitioning to the next action until permission is granted (for example, by receiving manual approval from an authorized IAM user). You might use an approval action when you want the pipeline to continue only after a successful code review, for example, or you want to control the time at which a pipeline transitions to a final Production stage. In this case, you can add a manual approval action to a stage just before Production, and approve it yourself when you're ready to release changes to the public.
- Every output artifact must have a unique name within the pipeline
Every input artifact for an action must match the output artifact of an action earlier in the pipeline
AWS SAM supports Amazon API Gateway APIs, AWS Lambda functions, and Amazon DynamoDB tables. You can use AWS CodePipeline with AWS CloudFormation and the AWS Serverless Application Model to continuously deliver your serverless applications.
Please note that you need to create the Elastic Beanstalk environment in a region that supports CodePipeline. https://aws.amazon.com/ko/blogs/devops/building-continuous-deployment-on-aws-with-aws-codepipeline-jenkins-and-aws-elastic-beanstalk/
