CI/CD
30 guides tagged “CI/CD”.
- How to Run a Coding Agent in CI Run it on pull requests with a read-only token, no secrets, a time budget, and a diff it can only propose — never push.
- How to Run a Security Review on Every Pull Request Wire a review into CI with a narrow scope, evidence-based output, and a human owner for verified high-severity findings.
- Build vs Deploy vs Release: What's the Difference? Building produces an artifact, deploying runs it, releasing exposes it. Separating the three is what makes rollback and canaries possible.
- Do You Need CI/CD for a Solo Project? A solo developer gets less from coordination and more from memory. The smallest pipeline worth maintaining, and what to skip.
- What Are the Stages of a CI/CD Pipeline? A CI/CD pipeline runs source, build, test, package, deploy, and verify. Here is what each stage outputs and which ones a small project can skip.
- Continuous Delivery vs Continuous Deployment: Which Do You Need? Delivery leaves the production push to a person; deployment ships every passing build. The difference is who owns release risk.
- Continuous Integration vs Continuous Delivery: What's the Difference? CI proves every commit integrates and passes tests. Continuous delivery keeps it releasable. Different practices, different failure modes.
- What Are the DORA Metrics (and How Do You Measure Them)? The four DORA metrics measure delivery speed and stability: deployment frequency, lead time, change failure rate, and time to restore.
- How to Speed Up CI Builds (Without Skipping Tests) Slow pipelines get bypassed. Cut time with dependency caching, parallel jobs, test splitting, and smaller images - not by disabling checks.
- What Is a Build Artifact (and Why Does Yours Keep Breaking)? A build artifact is the immutable output of a build, identified by a digest. Passing it between stages stops environments from diverging.
- What Is a CI Runner (and When Do You Need Your Own)? The runner executes pipeline jobs. Hosted runners are ephemeral and easy; self-hosted ones are cheaper at scale and a credential risk if done wrong.
- What Is Trunk-Based Development? Trunk-based development means short-lived branches and daily merges into one shared branch. It reduces integration risk and suits AI-agent teams.
- Non-Human Identities in CI/CD: Where They Leak CI concentrates production credentials: repository secrets, deploy keys, cloud keys, and tokens in logs. Most leaks happen in the pipeline, not the app.
- Deploying AI-Generated Apps to Production: A Vibecoder's Checklist Your AI wrote the app. Now here's every step between 'it works on my machine' and 'it's running in production.' Deployment, monitoring, secrets, databases, and the checklist your AI didn't include.
- DevOps for AI Builders: What You Need to Know When Your AI Writes the Infra Your AI coding assistant writes CI/CD pipelines, Dockerfiles, and Terraform. Here's every DevOps concept you need to understand so it doesn't burn production down. 60+ linked guides.
- Feature Flags vs Feature Toggles: What's the Difference? Feature flag and feature toggle are often used interchangeably, but flags are for release management and toggles are for runtime behavior. Learn the distinction, the four types, and how to use them without creating tech debt.
- Why Does the AI's Code Keep Failing Linting (and How to Fix It)? Your AI assistant generates code that fails every lint rule. Here's why, which rules to enforce in CI, and how to auto-fix the AI's output before it merges.
- What Is Continuous Delivery? Continuous delivery means every code change is automatically built, tested, and kept ready to deploy at any moment. Learn how it differs from CI and continuous deployment.
- How to Set Up a CI/CD Pipeline With GitHub Actions A step-by-step GitHub Actions tutorial: build and test a Node.js app on every push and deploy on release. Includes a working workflow file.
- What Is DevSecOps? DevSecOps builds security into every stage of the software pipeline instead of bolting it on at the end. Learn the principles and where to start.
- What Is a Blue-Green Deployment? A blue-green deployment runs two identical environments and swaps traffic between them, giving instant rollback. Learn how it works and its costs.
- What Is a Canary Deployment? A canary deployment rolls a new version out to a small slice of users first, watching for errors before expanding. Learn how it limits blast radius.
- What Is GitOps? GitOps makes a Git repository the single source of truth for infrastructure, with automated tools reconciling the real system to match it.
- What Is a Feature Flag? Feature flags let you ship dark and enable later. But there are 4 types — release, experiment, ops kill-switches, and permission gates — and mixing them up creates tech debt.
- Secret Scanning vs SAST vs DAST: Which Do You Actually Need? Three scanners that get installed interchangeably: one finds committed credentials, one reads your code for flaws, one attacks the running app. Different inputs, different findings.
- Why Does My Build Pass Locally but Fail in CI? The nine differences between your laptop and a CI runner that break builds: lockfiles, runtimes, case sensitivity, environment, caching, and hidden state.
- How to Add Security Scanning to Your CI/CD Pipeline Add secret, dependency, and SAST scanning to a GitHub Actions pipeline. A practical tutorial with working workflow YAML.
- How to Set Up GitOps With Argo CD A step-by-step tutorial to install Argo CD, connect it to a Git repo, and deploy an app declaratively — so Git becomes your source of truth.
- Rolling vs Blue-Green vs Canary Deployments: Which Should You Pick? Compare rolling, blue-green, and canary deployment strategies: downtime, rollback speed, cost, and complexity — with a decision table.
- What Is CI/CD? CI/CD automates building, testing, and deploying code so changes reach production safely and often. Learn how it works and why AI-generated projects need it.