This is the first series of my CI/CD with AWS CodePipeline and ECS.
Product feedback from customers is something any company doesn't want to joke with, which requires to be companies to be releasing software faster than ever. However, many of these companies struggle to deliver their software to their users. Delays happen when there are no feedback loops and a smooth delivery pipeline to rollout features with or without human intervention.
Automated release pipelines for fast and reliable application and infrastructure changes are made possible by AWS CodePipeline. Every time you make a code change, CodePipeline uses your defined release model to automate your release process's build, test, and deployment parts.
- Easy to use: AWS CodePipeline has an easy-to-use process workflow where you can describe what your release process looks like.
- Third-Party Integration: You can directly integrate the code pipeline with your CI tools like Jenkins or TeamCity.
- Custom plugins: AWS CodePipeline allows you to integrate your custom systems. You can register a custom action that allows you to hook your servers into your Pipeline by integrating the CodePipeline open-source agent with your servers.
- Declarative templates: AWS CodePipeline lets you define your pipeline structure using a JSON document that specifies your release workflow's stages and actions.
These are the terminologies you will come across when using AWS CodePipeline.
Pipeline: A pipeline defines your release process workflow and describes how a new code change progresses through the release cycle of your software delivery.
Actions: an action is part of the sequence in a pipeline stage.
Stages: Stage is the logical division in your workflow. Each stage is made up of a sequence of actions. Your Pipeline has at least two stages, Source, which is required, and any other.
In this article, I've explained how CI/CD, which AWS CodePipeline streamlines, is a crucial component of today's modern feature or product delivery. I also go through some of AWS CodePipeline's functionality and some of its components.
The next post in this series will walk you through setting up a Pipeline to build a docker image and using Github as our Source.
Kindly subscribe to my newsletter so you can be the first person to know when I release the next post.
Thanks for reading!