Ravindra BagaleCourses & study guides मराठी

Ravi Sir's Cards › DevOps

Chapter 8: CI/CD Concepts: Cards

मराठी cards · Open the chapter

Revision cards

CI/CD is a practice, not a tool. Teams think buying a tool gives them CI/CD. Without the habits, nothing improves.
Revision card 1 of 14: CI/CD is a practice, not a tool · Download PNG · Open card page

Lesson: 8.0 A Netflix-style release — CI/CD is the practice, Jenkins is a tool

Why a pipeline: stop the ship on a failed check. People forget steps when releasing by hand, and bugs reach users.
Revision card 2 of 14: Why a pipeline: stop the ship on a failed check · Download PNG · Open card page

Lesson: 8.1 Why a pipeline — stop the ship on a failed check

CI/CD pipeline stages: lint, test, build, push, deploy. Manual releases forget steps. A pipeline runs the same checks in the same order on every code push.
Revision card 3 of 14: CI/CD pipeline stages: lint, test, build, push, deploy · Download PNG · Open card page

Lesson: 8.2 Pipeline stages — lint → test → build → push → deploy

Artifacts and versioning. If you rebuild for each environment, you may ship something different from what you tested.
Revision card 4 of 14: Artifacts and versioning · Download PNG · Open card page

Lesson: 8.3 Artifacts and versioning

Environments: dev, staging, production. Testing straight on production risks real users.
Revision card 5 of 14: Environments: dev, staging, production · Download PNG · Open card page

Lesson: 8.4 Environments — dev, staging, production

Fail fast and quality gates. Waiting 30 minutes to learn about a typo wastes time.
Revision card 6 of 14: Fail fast and quality gates · Download PNG · Open card page

Lesson: 8.5 Fail fast and quality gates

Manual approval for production. Some changes need a human yes before reaching real users.
Revision card 7 of 14: Manual approval for production · Download PNG · Open card page

Lesson: 8.6 Manual approval for production — when and why

CI vs CD vs deploy vs release. Deploy and release sound the same but are different moments.
Revision card 8 of 14: CI vs CD vs deploy vs release · Download PNG · Open card page

Lesson: 8.7 CI vs CD vs deploy vs release (refresh)

What a junior watches on a red pipeline. A red pipeline blocks the whole team until fixed.
Revision card 9 of 14: What a junior watches on a red pipeline · Download PNG · Open card page

Lesson: 8.8 What a junior watches on a red pipeline

Metrics of a healthy pipeline. A slow or often-red pipeline makes people skip it.
Revision card 10 of 14: Metrics of a healthy pipeline · Download PNG · Open card page

Lesson: 8.8b Metrics of a healthy pipeline (plain English)

Who owns a red build. If nobody owns a red build, it stays red and everyone suffers.
Revision card 11 of 14: Who owns a red build · Download PNG · Open card page

Lesson: 8.8c Who owns a red build?

CI/CD anti-patterns. Small bad habits slowly break trust in the pipeline.
Revision card 12 of 14: CI/CD anti-patterns · Download PNG · Open card page

Lesson: 8.9 Anti-patterns (spot them early)

Versioning and release notes. Users and teams need to know what changed between versions.
Revision card 13 of 14: Versioning and release notes · Download PNG · Open card page

Lesson: 8.10 Versioning and release notes (lightweight)

Lab: design the badge-api pipeline on paper. Writing pipeline code before the design leads to missing steps.
Revision card 14 of 14: Lab: design the badge-api pipeline on paper · Download PNG · Open card page

Lesson: 8.11 Lab — design badge API pipeline on paper

Interview cards

Is CI/CD a tool? No. It's a practice: small changes, tested on every push, released safely. Tools only help.
Interview card 1 of 14: Is CI/CD a tool? · Download PNG · Open card page

Lesson: 8.0 A Netflix-style release — CI/CD is the practice, Jenkins is a tool

Why use a pipeline? It runs the same checks every time and stops when one fails, so broken code doesn't ship.
Interview card 2 of 14: Why use a pipeline? · Download PNG · Open card page

Lesson: 8.1 Why a pipeline — stop the ship on a failed check

Name the usual CI/CD pipeline stages. Lint → test → build → push → deploy. Cheap checks first; any failure stops the run.
Interview card 3 of 14: Name the usual CI/CD pipeline stages. · Download PNG · Open card page

Lesson: 8.2 Pipeline stages — lint → test → build → push → deploy

Why build once and deploy the same artifact? So production runs exactly what was tested. Rebuilding can pull different libraries.
Interview card 4 of 14: Why build once and deploy the same artifact? · Download PNG · Open card page

Lesson: 8.3 Artifacts and versioning

Why have dev, staging and production? Each catches different problems before real users see them. Staging copies prod for a final check.
Interview card 5 of 14: Why have dev, staging and production? · Download PNG · Open card page

Lesson: 8.4 Environments — dev, staging, production

What does fail fast mean in a pipeline? Run the quickest checks first, so most problems are found in seconds, not after a long build.
Interview card 6 of 14: What does fail fast mean in a pipeline? · Download PNG · Open card page

Lesson: 8.5 Fail fast and quality gates

When do you add manual approval? Before production for risky or regulated apps, like banks and payments. Log who approved.
Interview card 7 of 14: When do you add manual approval? · Download PNG · Open card page

Lesson: 8.6 Manual approval for production — when and why

What is the difference between deploy and release? Deploy: new code is on servers. Release: users can use it. A feature flag separates them.
Interview card 8 of 14: What is the difference between deploy and release? · Download PNG · Open card page

Lesson: 8.7 CI vs CD vs deploy vs release (refresh)

The pipeline is red. What do you do first? Find the red stage, read the first error, check the last commit, then fix or revert.
Interview card 9 of 14: The pipeline is red. What do you do first? · Download PNG · Open card page

Lesson: 8.8 What a junior watches on a red pipeline

How do you know a pipeline is healthy? Short duration, high success rate, and quick time to fix when red.
Interview card 10 of 14: How do you know a pipeline is healthy? · Download PNG · Open card page

Lesson: 8.8b Metrics of a healthy pipeline (plain English)

Who should fix a red build on main? The author of the change that broke it, quickly, or revert it to unblock others.
Interview card 11 of 14: Who should fix a red build on main? · Download PNG · Open card page

Lesson: 8.8c Who owns a red build?

Name some CI/CD anti-patterns. Skipping tests, rebuilding per environment, manual hotfixes on servers, and ignoring red builds.
Interview card 12 of 14: Name some CI/CD anti-patterns. · Download PNG · Open card page

Lesson: 8.9 Anti-patterns (spot them early)

Explain semantic versioning. MAJOR.MINOR.PATCH: major = breaking, minor = new feature, patch = bug fix.
Interview card 13 of 14: Explain semantic versioning. · Download PNG · Open card page

Lesson: 8.10 Versioning and release notes (lightweight)

How would you design a pipeline for a small API? PRs: lint + test. Main: build, scan, push image, deploy staging. Prod: approval, deploy, smoke test.
Interview card 14 of 14: How would you design a pipeline for a small API? · Download PNG · Open card page

Lesson: 8.11 Lab — design badge API pipeline on paper

Comparison cards

CI vs CD (Continuous Integration vs Continuous Delivery). CI (Continuous Integration): every code push is built and tested automatically, many times a day.CD (Continuous Delivery): every change that passes CI is packed and made ready to release to users.
Comparison card 1 of 3: CI vs CD (Continuous Integration vs Continuous Delivery) · Download PNG · Open card page

Lesson: 8.7 CI vs CD vs deploy vs release (refresh)

Deploy vs Release. Deploy: put new code on servers.Release: let users use the new feature.
Comparison card 2 of 3: Deploy vs Release · Download PNG · Open card page

Lesson: 8.7 CI vs CD vs deploy vs release (refresh)

Continuous Delivery vs Continuous Deployment. Delivery: every good change is ready; a human clicks to release.Deployment: every good change goes live automatically.
Comparison card 3 of 3: Continuous Delivery vs Continuous Deployment · Download PNG · Open card page

Lesson: 8.6 Manual approval for production — when and why