Software Release Phases vs AWS CI CD Services

What-so-ever may be the software development methodology (Agile or Feature Driven Development) the company follows for their software development, the ultimate goal is take the code changes from source to production faster than ever which ideally encompasses 4 phases – Source, Build, Test & Deploy. This forms software release phases in general.

Let’s see where does the AWS CI CD Services fits in the above software release phases.

• Source phase is where the complete Code Management happens comprising check-in source code, peer review, version control and the AWS CodeCommit is all around that.
• In Build phase, you will compile the code, run unit test or create container images and the AWS CodeBuild is designed for that.
• In Test phase, you will perform the Integration, UI, Load, Stress Test by integrating with various third-party tools.
• In Deploy phase, the package generated in the build phase will be deployed to the target environment, be it Dev, QA, PreProd or Prod.
• AWS CodeDeploy service is here to make your life simple where deploying to thousands of servers is just as easy as deploying to 1. 
• AWS CodePipeline is an end-to-end solution, which comes handy to glue all these services. CodePipeline enables you to rapidly deliver features and updates with high quality through the automation of your build, test, and release process.

If you are wondering why am I using the term AWS CI CD Services instead of AWS Developer Tools, its just because in this session, we will be talking only about AWS CodeCommit, AWS CodeBuild, AWS CodeDeploy & AWS CodePipeline but not AWS Code-Star, AWS Cloud-9 & AWS X-ray.