<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ci-Cd on My Blog</title><link>https://hugo-blog.aitbytes.dev/tags/ci-cd/</link><description>Recent content in Ci-Cd on My Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 11 Jun 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://hugo-blog.aitbytes.dev/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>The GitLab CI Playbook: Running 75,000 Jobs a Day</title><link>https://hugo-blog.aitbytes.dev/posts/2026-06-11-gitlab-ci-playbook/</link><pubDate>Thu, 11 Jun 2026 07:00:00 +0000</pubDate><guid>https://hugo-blog.aitbytes.dev/posts/2026-06-11-gitlab-ci-playbook/</guid><description>&lt;p&gt;A team at a large enterprise runs 75,000 GitLab CI jobs every day. Their setup is almost boring.&lt;/p&gt;
&lt;p&gt;EKS for runner management. Official Helm chart. One runner namespace per team. Fleeting plugin for autoscaling on spot instances.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;We don&amp;rsquo;t think about it,&amp;rdquo; they said. &amp;ldquo;It just works.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the goal. Getting there requires some deliberate architectural decisions. Here&amp;rsquo;s what teams running GitLab CI at scale have figured out.&lt;/p&gt;
&lt;h2 id="the-hierarchy-that-makes-everything-else-work"&gt;The Hierarchy That Makes Everything Else Work&lt;/h2&gt;
&lt;p&gt;GitLab CI isn&amp;rsquo;t just about pipelines. It&amp;rsquo;s about the organizational structure those pipelines inherit from.&lt;/p&gt;</description></item></channel></rss>