CI/CD Pipelines & Automation

Continuous integration and continuous delivery automate the path from a commit to a tested, deployable, and deployed artifact. These guides cover building reliable pipelines — running tests and linting on every change, building and versioning artifacts, and deploying safely with strategies like blue-green and canary releases.

The emphasis is on fast, trustworthy feedback and safe releases: caching, parallelization, secrets handling, and gates that catch regressions before users do.

Related:DevOps Docker Kubernetes

GitLab is capping unauthenticated API calls at 60 an hour starting October 19, and the preview windows land before most teams will have noticed.

••last week

GitLab's New Rate Limits: What to Fix Before Oct 19

GitLab is capping unauthenticated API calls at 60 an hour starting October 19, and the preview windows land before most teams will have noticed.

Kiril Urbonas·54

Read article

Microsoft's Storm-3068 report used zero malware to steal Kubernetes credentials, just a password reset, a pipeline edit, and permissions nobody had scoped down.

••2 weeks ago

Storm-3068: A CI/CD Pipeline Is a Kubeconfig Exfiltration Machine

Microsoft's Storm-3068 report used zero malware to steal Kubernetes credentials, just a password reset, a pipeline edit, and permissions nobody had scoped down.

Kiril Urbonas·10

Read article

A background cleanup job saturated the database behind GitHub's permission checks, and the safeguard pacing it watched only replica lag. Throttle on more than one signal.

••0 months ago

GitHub's September 13 Outage: One Cleanup Job, 28 Services

A background cleanup job saturated the database behind GitHub's permission checks, and the safeguard pacing it watched only replica lag. Throttle on more than one signal.

Kiril Urbonas·16

Read article

Running a coding agent on a laptop is a preference. Running one in a pipeline is an architecture decision about credentials, sandboxing, and non-interactive failure.

••last month

AI CLI Agents in CI: Claude Code vs Codex CLI vs Gemini CLI

Running a coding agent on a laptop is a preference. Running one in a pipeline is an architecture decision about credentials, sandboxing, and non-interactive failure.

Kiril Urbonas·26

Read article

The keyv compromise reached 444 packages and over two billion monthly installs through preinstall scripts. The controls that actually stop it are boring and mostly free.

••last month

Your CI Runner Is the Target: Hardening Against npm Worms

The keyv compromise reached 444 packages and over two billion monthly installs through preinstall scripts. The controls that actually stop it are boring and mostly free.

Kiril Urbonas·21

Read article

Your pipeline holds the keys to production and signs off on everything you ship, so harden both the pipeline itself and the artifacts it builds.

••2 months ago

How to Secure Your CI/CD Pipeline (DevSecOps)

Your pipeline holds the keys to production and signs off on everything you ship, so harden both the pipeline itself and the artifacts it builds.

Kiril Urbonas·23

Read article

Most GitHub Actions pain comes from the same handful of jobs done wrong. This is the map: the recipes that make pipelines fast, secure, and cheap.

••2 months ago

GitHub Actions Recipes — The Practical Guide

Most GitHub Actions pain comes from the same handful of jobs done wrong. This is the map: the recipes that make pipelines fast, secure, and cheap.

Kiril Urbonas·14

Read article

A prioritized toolkit for cutting CI time: measure the critical path first, then cache, parallelize, run only what changed, and shrink the work itself.

••2 months ago

How to Speed Up a Slow CI Pipeline

A prioritized toolkit for cutting CI time: measure the critical path first, then cache, parallelize, run only what changed, and shrink the work itself.

Kiril Urbonas·34

Read article

Run only the CI jobs a change actually affects using if conditionals, trigger path filters, and per-job path detection in a monorepo.

••2 months ago

Conditional Jobs and Path Filters in GitHub Actions

Run only the CI jobs a change actually affects using if conditionals, trigger path filters, and per-job path detection in a monorepo.

Kiril Urbonas·45

Read article

Stop re-downloading the same packages on every CI run by caching dependencies with keys that actually hit.

••2 months ago

Cache Dependencies in GitHub Actions

Stop re-downloading the same packages on every CI run by caching dependencies with keys that actually hit.

Kiril Urbonas·44

Read article

A practical guide to building, tagging, caching, and pushing Docker images from GitHub Actions using buildx, GHCR, and multi-arch builds.

••2 months ago

Build and Push Docker Images in GitHub Actions

A practical guide to building, tagging, caching, and pushing Docker images from GitHub Actions using buildx, GHCR, and multi-arch builds.

Kiril Urbonas·44

Read article

A practical guide to matrix builds in GitHub Actions that tests across versions and platforms without burning your monthly minutes.

••2 months ago

GitHub Actions Matrix Builds That Don't Waste Minutes

A practical guide to matrix builds in GitHub Actions that tests across versions and platforms without burning your monthly minutes.

Kiril Urbonas·33

Read article

Frequently asked questions

What is CI/CD?

CI (continuous integration) automatically builds and tests every code change; CD (continuous delivery/deployment) automatically prepares and releases those changes to production. Together they make releases frequent, small, and low-risk.

What is the difference between continuous delivery and continuous deployment?

Continuous delivery keeps every change ready to release with a manual approval step before production; continuous deployment removes that step, automatically releasing every change that passes the pipeline.