Ravindra BagaleCourses & study guides मराठी

Ravi Sir's Cards › DevOps

Chapter 30: Artifacts, Release Patterns and Quality Gates: Cards

मराठी cards · Open the chapter

Revision cards

Artifacts by name. Files called app.zip can't tell you which build they came from.
Revision card 1 of 7: Artifacts by name · Download PNG · Open card page

Lesson: 30.1 Artifacts by name

Email and Slack notifications. Too many messages get muted. Too few and nobody fixes red builds.
Revision card 2 of 7: Email and Slack notifications · Download PNG · Open card page

Lesson: 30.2 Email and Slack

Blue-green deployment. Updating servers in place can cause downtime and slow rollback.
Revision card 3 of 7: Blue-green deployment · Download PNG · Open card page

Lesson: 30.3 Blue-green

Canary release. A bug that hits all users at once is a big outage.
Revision card 4 of 7: Canary release · Download PNG · Open card page

Lesson: 30.4 Canary

Rollback. When a release breaks, fixing forward can take too long.
Revision card 5 of 7: Rollback · Download PNG · Open card page

Lesson: 30.5 Rollback

Test layers. Only slow end-to-end tests make pipelines slow and flaky.
Revision card 6 of 7: Test layers · Download PNG · Open card page

Lesson: 30.6 Test layers

Quality gates and database migrations. A database change that breaks the old app version makes rollback impossible.
Revision card 7 of 7: Quality gates and database migrations · Download PNG · Open card page

Lesson: 30.7 Quality gates and database migrations

Interview cards

How do you name build artifacts? app-version-build, like badge-1.4.0-57.zip, so anyone can trace it to a build and commit.
Interview card 1 of 7: How do you name build artifacts? · Download PNG · Open card page

Lesson: 30.1 Artifacts by name

How do you set Jenkins notifications without spam? Notify on failure and fixed for main; the author for PRs. Not on every success.
Interview card 2 of 7: How do you set Jenkins notifications without spam? · Download PNG · Open card page

Lesson: 30.2 Email and Slack

What is blue-green deployment? Two full environments. Deploy to the idle one, test it, then switch traffic all at once. Switch back to roll back.
Interview card 3 of 7: What is blue-green deployment? · Download PNG · Open card page

Lesson: 30.3 Blue-green

What is a canary release? Send a small % of traffic to the new version, watch errors and latency, then increase.
Interview card 4 of 7: What is a canary release? · Download PNG · Open card page

Lesson: 30.4 Canary

How do you roll back a bad release? Redeploy the last good artifact, or use rollout undo / helm rollback. Have a tested rollback job.
Interview card 5 of 7: How do you roll back a bad release? · Download PNG · Open card page

Lesson: 30.5 Rollback

What is the test pyramid? Many fast unit tests, fewer integration tests, few slow end-to-end tests.
Interview card 6 of 7: What is the test pyramid? · Download PNG · Open card page

Lesson: 30.6 Test layers

How do you deploy database changes safely? Use versioned migrations that are backward compatible: expand first, contract later, with a backup.
Interview card 7 of 7: How do you deploy database changes safely? · Download PNG · Open card page

Lesson: 30.7 Quality gates and database migrations

Comparison cards

Blue-green vs Canary. Blue-green: two full copies, switch all traffic at once.Canary: send a small part of traffic first, then grow.
Comparison card 1 of 3: Blue-green vs Canary · Download PNG · Open card page

Lesson: 30.3 Blue-green

Rollback vs fix forward. Rollback: go back to the last good version.Fix forward: ship a new fix quickly.
Comparison card 2 of 3: Rollback vs fix forward · Download PNG · Open card page

Lesson: 30.5 Rollback

Unit test vs end-to-end test. Unit: tests one function alone.End-to-end: tests the whole app like a user.
Comparison card 3 of 3: Unit test vs end-to-end test · Download PNG · Open card page

Lesson: 30.6 Test layers