8.1 Why a pipeline — stop the ship on a failed check
Imagine a factory conveyor for tiffin boxes. If one box fails quality check, you stop the belt before thousands of bad boxes ship. Software needs the same habit.
CI (Continuous Integration) — every change merges into a shared line often, and an automated build/test run proves the change did not break the basics.
CD can mean Continuous Delivery (always ready to deploy to production, often with a human click) or Continuous Deployment (every green build goes to production automatically). Interviews care that you know the difference; companies choose based on risk.
Why it matters for an Instagram-style badge API : a broken badge API at lunch costs orders. A pipeline that fails on red tests protects lunch better than "it worked on my laptop."
| Manual heroics | Pipeline |
|---|---|
| Remember to run tests | Tests run on every PR |
| "Which zip did we deploy?" | Tagged artifact / image digests |
| Friday night surprise | Same stages every time |
Ravindra Bagale's Tip
Interview madhe "CI/CD = Jenkins" ulta sangu naka. CI/CD = practice; Jenkins/Actions = tools. Pehle flow, nantar button. Lakshat theva!