Learning AWS Day by Day — Day 66 — AWS CodePipeline

Learning AWS Day by Day — Day 66 — AWS CodePipeline

Exploring AWS !!

Day 66

AWS CodePipeline

AWS has developer tools like AWS CodeCommit, CodeBuild, CodeDeploy, CloudShell, and many more. Today, we will be covering AWS CodePipeline.

CodePipeline is a continuous delivery service, which helps you in building and automating the steps required to release your software. The process involves modelling and automating the steps when deploying the software or application. The whole pipeline can be maintained and automated at every step continuously.

CI/CD — Continuous Integration and Continuous Delivery
Every software that goes through the pipeline is built, tested, automated and delivered or deployed to the production. There is a manual intervention required before the final push, it might be a person, business rule or an automated test, this is because the product before directly getting deployed to production shall be checked again the final time, as not all changes need to be deployed directly.
Continuous integration is where the team uses a version control mechanism like Git, and keep integrating their work to a final destination like main or master branch. Each change made is built and verified, so that any integration errors can be noticed quickly and get resolved. Continuous integration mainly focuses on building and testing your code, whereas delivery focuses entirely on the release and deployment process of your application.

With CodePipeline you can do following:
Automate your releases from end to end by building, testing an deploying the application. The changes can be controlled from moving through pipeline by adding manual interventions for a push.
You can define each and every stage according to you criteria and requirements.
The delivery can be speedy using automated process and the quality can be maintained through testing.
You can also use supported third party tools for building and deploying the application.
The progress of your pipeline can be viewed instantly, the failure reasons, and how many stages are pending as well as how many are yet to be completed, everything is visible. You can view details about the source revisions used in the latest pipeline execution in each stage, and manually rerun any pipeline.

CodePipeline types:
V1 type pipelines having JSON structure containing standard pipeline, stage, and action-level parameters.
V2 type pipelines having the structure just like V1 type, along with additional parameters for release safety and trigger configuration.

Leave a Reply

Your email address will not be published. Required fields are marked *