Introduction:
Hey, cloud enthusiasts! Welcome back to the adventure-packed journey of the “30 Days of AWS” series. 🌐💻 Today, we’re strapping in for a thrilling ride into the heart of modern software delivery — it’s Day 15, and we’re diving headfirst into the enchanting world of AWS CodePipeline! 🤖🛠️
Buckle up your virtual seatbelts because, in this instalment, we’re not just talking pipelines; we’re unleashing the magic of continuous delivery with AWS CodePipeline! 🌈✨ If you’ve ever wondered how the wizards of DevOps seamlessly weave code from development to deployment, stick around, because we’re about to unveil the secrets! 🧙♂️🚀
Whether you’re a seasoned cloud sorcerer or a curious coder on a quest for knowledge, this blog is your map to mastering CodePipeline sorcery. 🗺️🔍 Are you ready to automate, deploy, and conquer the challenges of modern software development? Then let’s embark on this exhilarating journey together! 🚀🔥
Grab your wands (or keyboards) and join us as we unravel the enchantment of AWS CodePipeline in today’s magical blog post! 📜💫 Let the continuous delivery adventure begin! 🌐🚀
What is AWS Code Pipeline?
AWS CodePipeline is a continuous delivery service that enables you to model, visualize, and automate the steps required to release your software. With AWS CodePipeline, you model the full release process for building your code, deploying to pre-production environments, testing your application and releasing it to production. AWS CodePipeline then builds, tests, and deploys your application according to the defined workflow every time there is a code change. You can integrate partner tools and your own custom tools into any stage of the release process to form an end-to-end continuous delivery solution.
Why should I use AWS CodePipeline?
By automating your build, test, and release processes, AWS CodePipeline enables you to increase the speed and quality of your software updates by running all new changes through a consistent set of quality checks.
This is a workflow of our today’s blog.
Let’s Get started:
In our previous blog we had created the 4 steps:
- AWS Code Commit
- AWS Code Build
- AWS Cloud Artifact
- AWS Code Deploy
If you have not seen these blogs then please see these blogs for better understanding.
[🚀 Day 12: AWS CodeCommit — Version Control in the Cloud
Introduction:purushotamsharma.medium.com](https://purushotamsharma.medium.com/day-12-aws-codecommit-version-control-in-the-cloud-6855351c2952 "purushotamsharma.medium.com/day-12-aws-code..")
[Unleashing CodeBuild Magic: A Deep Dive into AWS Development | 30 Days of AWS — Day 13" 🚀💻
Introduction:purushotamsharma.medium.com](https://purushotamsharma.medium.com/unleashing-codebuild-magic-a-deep-dive-into-aws-development-30-days-of-aws-day-13-9b1793bfc00e "purushotamsharma.medium.com/unleashing-code..")
[Day 14: Unleashing the Deployment Dynamo — A Deep Dive into AWS CodeDeploy!🚀✨
Introduction:purushotamsharma.medium.com](https://purushotamsharma.medium.com/day-14-unleashing-the-deployment-dynamo-a-deep-dive-into-aws-codedeploy-d96f5156ebad "purushotamsharma.medium.com/day-14-unleashi..")
Today we will be creating the Piepline and automating this workflow.
Let’s go:
- First of all, go to the AWS Management Console and navigate to the AWS Code pipeline service.
- You will see this type of user interface:
- Now click on the Create Pipeline.
- Now write the pipeline name and after that select v2 as the pipeline type.
- Select New Service role.
- Now click on the next.
- Now, add the source
- If you are following my blog then select AWS code commit
- Now Write the repo name
- Select Branch
- Click on the next.
- In the build provide select the AWS code build as a build provider.
- Now select the Project name and select the single build as the build type.
- Now select the deploy provider
Se
- Now select your application name and deployment group.
- On this is last but not least step review and click on the Create Pipeline.
- Our Pipeline is successfully created, Congratulation everyone…
- Our source has successfully succeeded.
- Build also created.
- Congratulation our deploy process is also completed…
- Now let's see this project by accessing the public IP.
- Successfully deploy the project using the ci cd pipeline.
- Let’s check whether this pipeline is working or not
- If we change the code then the pipeline automatically should trigger
- Go to the AWS code commit and add a new file
- Click on the Add file and click on the Create file.
- Click on the commit changes.
- After clicking on the commit changes the pipeline automatically starts re-building.’
That’s all from my side in today’s blog.
If you like the blog then share it with your friends.
Happy Learning:))
My Github Profile:
[PurushotamSharma - Overview
Purusing MCA from Charusat University. PurushotamSharma has 39 repositories available. Follow their code on GitHub.github.com](https://github.com/PurushotamSharma "github.com/PurushotamSharma")
Github Repo for AWS series:
[GitHub - PurushotamSharma/30-Days-of-AWS-Adventure-
Contribute to PurushotamSharma/30-Days-of-AWS-Adventure- development by creating an account on GitHub.github.com](https://github.com/PurushotamSharma/30-Days-of-AWS-Adventure- "github.com/PurushotamSharma/30-Days-of-AWS-..")
Stay tuned for day 16.