BREAKING THE CI/CD PIPELINE BUT IT WILL NOT LEAK
Getting into the field of creating and building new projects in any desired track be it DevOps, AI, Cloud computing, and so on. It is…
Photo by Growtika on Unsplash
BREAKING THE CI/CD PIPELINE BUT IT WILL NOT LEAK
Getting into the field of creating and building new projects in any desired track be it DevOps, AI, Cloud computing, and so on. It is always something different and new one explores and learns from but any created project becomes more acknowledgeable and worth-building if it can be useful to others to understand and learn from the project.
Here, we are talking about making our built-in projects accessible to more other people which means deploying it for better understanding of one’s own projects and further revamping for good user experience.
Now, before deep diving into how we actually make that happen, we need to go understand some commonly occurring jargons used in technical work.
Starting off with a simple word “DEPLOYMENT”
Once, you enter into engineering field, this word comes very frequently around us and we are left baffled and wonder what this could possibly related to?It may be a simple word but holds much importance for successful implementation of our work to others.
‘Deployment is a process of making our work accessible and useable to others.’
This is the simplest definition for this term and far more easy to grasp for a beginner. Basically it means to put our work on live site to its audience from development environment. Our projects will then be live on internet and users will be able to use it easily.
Many options are available for deployment and some includes Netlify, Vercel, AWS Amplify, GCP(Google Cloud Platfom), Microsoft Azure etc. One can decide and explore for oneself on what to use based on their personal preference.
Next, “CI/CD Pipeline” which stands for (Continuous Integration/Continuous Delivery or Deployment), is a practice that makes it easier to build, test, and deploy code without manually doing it every time we brought change in our pre-written code.
a) CI [Continuous Integration]
. It focuses on integrating code changes frequently by automated tests and during automation, if test is failed ,the developer is notified about the same.
NOTE:- Both Continuous Delivery and Continuous Deployment are abbreviated as “CD”, but they differ in release automation.
b) CD [Continuous Delivery]
. After CI does its work, code is moved to Acceptance Testing and deployed to Staging Environment
. Here, manual deployment is needed
CD [Continuous Deployment]
. Process is the same as Continuous Delivery just deployment is automated rather than manual.
>> Working of CI/CD Pipeline
Developers push code to version control like Git -> Code there is compiled and built -> Automated testing is done -> Deploy for use using AWS Amplify or Vercel
For our first week of AWS (Summer Builder Cohort 2026) in DevOps + Cloud track, Our team CakePops, decided to keep our project simple and built a static website about the algorithm of CI/CD Pipeline in deploying any project using AWS Amplify, one of the AWS Service provided by Amazon which is accessible globally. Honestly speaking, we have never used this AWS Service before so it was interesting for us to try and see how different it is from others. Usually, Vercel is used for deployment of all of our projects but this time we took a different route by using AWS Amplify.
| Development of the Static Website |
Writing proper HTML Document from square one in code editor like VS Code
-
We wrote our HTML file using correct semantic tags for higher chances of SEO ranking.
-
Added necessary information and documentation.
Styling our HTML document with plain or vanilla CSS
-
Styled the website using external CSS stylesheet for better visual representation of the code.
-
Linked both the files using <link> tag in <head> tag of HTML file.
-
Emojis visible in the our website were added using the “font-awesome” library in CDN(Content Delivery Network) website.
-
Linked the library which is also another CSS stylesheet to our HTML document to access the emojis needed for our project.
| Pushing into GitHub |
Pushed our code into GitHub as repository
-Used GitHub actions having CI/CD tools for automation of our web application.
- Passed through CI/CD Pipeline for further deployment
| Deployment |
- We contemplated on what to use AWS Amplify or Vercel but ended up taking vercel into work.
-Our website got live and accessible for good use.
—Now comes the biggest challenge we faced while working on our website, taking AWS Amplify for deploying our static website.
Using AWS services as a novice was new to us but interesting at the same time, though it helped us a lot in understanding various concepts not just theortically but practically implementing by ourselves taught new learnings for our growing minds. But we did face some problems while using AWS Amplify to deploy our website so after discussing and experimenting, we ended up using Vercel, that we use every time.
~To overcome this challenge we are looking forward to properly learn about it and using it in our next project.
메타데이터
- post_id
- cb14e287ec54
- slug
- breaking-the-ci-cd-pipeline-but-it-will-not-leak-cb14e287ec54
- url
- https://medium.com/@triptimahavar/breaking-the-ci-cd-pipeline-but-it-will-not-leak-cb14e287ec54
- canonical_url
- https://medium.com/@triptimahavar/breaking-the-ci-cd-pipeline-but-it-will-not-leak-cb14e287ec54
- author_url
- https://medium.com/@triptimahavar
- status
- ok
- fetched_at
- 2026-06-22 12:55:45
