<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci on Nick DeTello - Nicholas DeTello</title><link>https://nick.detello.com/tags/ci/</link><description>Recent content in Ci on Nick DeTello - Nicholas DeTello</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nick.detello.com/tags/ci/index.xml" rel="self" type="application/rss+xml"/><item><title>A lease broker for one test board shared by CI and coding agents</title><link>https://nick.detello.com/blog/lease-broker-shared-test-board/</link><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><guid>https://nick.detello.com/blog/lease-broker-shared-test-board/</guid><description>Per-caller locks don&amp;rsquo;t compose when CI jobs, coding agents and I share one fragile board. What worked better was one broker that holds the board&amp;rsquo;s login, leases the board with two fencing tokens and quarantines it only when an outcome is unknown.</description></item><item><title>Isolating a Nix remote builder in a microVM on a shared host</title><link>https://nick.detello.com/blog/isolating-nix-remote-builder-microvm-shared-host/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://nick.detello.com/blog/isolating-nix-remote-builder-microvm-shared-host/</guid><description>Distributed builds lend spare capacity to CI, but build scripts execute untrusted code. I isolate them in a builder VM with its own kernel, restricted access and resources the host can reclaim.</description></item></channel></rss>