Skip to content
tezvyn:
Menu

CI/CD & Automation

GitHub Actions, Terraform, ArgoCD, IaC, pipelines

87 bites

Test yourself: Top 30 advanced CI/CD & Automation interview questions →Multiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.

Advanced everything in CI/CD & Automation, page 5

advanced2 min read

Monorepo vs. Polyrepo: One Repository or Many?

A monorepo is one repository for all projects, like a city; a polyrepo is one per project, like separate towns. Monorepos simplify code sharing and atomic refactors but require complex tooling. Polyrepos offer autonomy but can create dependency hell.

advanced2 min read

Git Cherry-Pick: Copy a Commit to Another Branch

Think of git cherry-pick as copying a single commit's changes from one branch and reapplying them as a new commit on another. It's for backporting a bug fix without merging an entire feature branch.

GitFlow: A Branching Model for Versioned Releases
advanced2 min read

GitFlow: A Branching Model for Versioned Releases

GitFlow organizes your repo around two main branches: master for production and develop for integration. It's designed for projects with distinct, numbered releases, like desktop apps, not for continuously delivered web apps where simpler models are…

Idempotency: Safe to Retry Automation
advanced2 min read

Idempotency: Safe to Retry Automation

Idempotent automation ensures an operation has the same effect whether run once or many times. This is vital for safely retrying failed CI/CD jobs or configuration scripts. The footgun: thinking it means 'no side effects'.

GitOps: Your Git Repo is the Single Source of Truth
advanced2 min read

GitOps: Your Git Repo is the Single Source of Truth

GitOps makes a Git repo the single source of truth for your infrastructure's desired state. An automated process makes production match what's declared in Git, enabling continuous deployment.

advanced2 min read

Immutable Infrastructure: Treat Servers Like Cattle, Not Pets

Immutable infrastructure means you never modify running servers. To deploy, you replace them with new ones built from a golden image. This is key for CI/CD and autoscaling, ensuring consistency. The footgun is configuration drift from manual, one-off fixes.

advanced2 min read

Pipeline as Code: Versioning Your Build Process

Treat your CI/CD pipeline not as clicks in a UI, but as a version-controlled file (Jenkinsfile) living with your code. This enables automated, reviewable build processes for every branch. The footgun is defining pipelines in the UI, creating a black box.

We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.

See open roles