Operations | Monitoring | ITSM | DevOps | Cloud

Last updated: April 2026 Playbooks that run every task every time aren't really automation. They're scripts. Real playbooks make decisions: only restart a service when its config changed, only install a package on Debian hosts, only send an alert when a prior task failed. That decision-making comes from Ansible conditionals.

Last month I was making a change to sx, our CLI. I updated a core flow, adding external catalogs as a source for sx add. Small change. Then came the testing. I knew I was messing with a core flow and wanted to be sure I hadn't broken anything. I spent about forty-five minutes setting up an isolated environment. Spinning up Docker. Fighting with tmux. Getting a clean install state I could run through the TUI a few times. Forty-five minutes of my afternoon that produced zero code. I complained in Slack.

A rolling deployment updates running application instances in batches, replacing old instances with new ones while the application keeps serving traffic. The concept applies to any system that can run multiple instances of an application, but Kubernetes has it built in as the default deployment strategy. Kubernetes terminates an old pod only after its replacement passes the configured readiness check, so no requests land on an unready instance.

CircleCI is part of the latest wave of Codex plugin integrations, joining the directory alongside other popular development tools like Vercel, Cloudflare, Figma, Notion, Sentry, Hugging Face, Linear, and more. If you’re using Codex, you already know that writing code is rarely the hardest part of your job. It’s the delays, interruptions, and context switching that start when that code breaks on its way to production. The CircleCI Codex plugin closes that gap.