<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci-Cd on GeekyRyan</title><link>https://rnemeth90.github.io/tags/ci-cd/</link><description>Recent content in Ci-Cd on GeekyRyan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 22 Apr 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://rnemeth90.github.io/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Ring-Based Release Process for Independent Team Execution</title><link>https://rnemeth90.github.io/projects/2025-04-22-ring-based-release-process/</link><pubDate>Tue, 22 Apr 2025 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2025-04-22-ring-based-release-process/</guid><description>&lt;p&gt;Build a ring-based release process so the release team could run deployments without needing engineering to babysit every release. Ring-based releases are straightforward in theory (roll through internal, then limited customer set, then everyone), but operationalizing it for a non-engineering team meant more than just the mechanics.&lt;/p&gt;&#10;&lt;p&gt;It took:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Aligning versioning across multiple repos so a &amp;ldquo;release&amp;rdquo; was actually a coherent unit, not a loose collection of independently-versioned pieces.&lt;/li&gt;&#10;&lt;li&gt;Tagging artifacts and tickets consistently so you could always trace what code and what work was in a given release.&lt;/li&gt;&#10;&lt;li&gt;Building enough guardrails and automation that the release team could run the whole thing confidently without checking with engineering for every step.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The win wasn&amp;rsquo;t the ring pattern itself - it was taking knowledge that lived in engineers&amp;rsquo; heads and turning it into a process someone else could own and execute.&lt;/p&gt;</description></item><item><title>Rebuilding a Lab Environment Deployment Pipeline From Scratch</title><link>https://rnemeth90.github.io/projects/2023-09-08-rebuilding-the-lab-deployment-pipeline/</link><pubDate>Fri, 08 Sep 2023 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2023-09-08-rebuilding-the-lab-deployment-pipeline/</guid><description>&lt;p&gt;Lab and test environments have a tendency to accumulate complexity over successive iterations of &amp;ldquo;just add one more special case.&amp;rdquo; By the millionth version of our lab deployment pipeline, it had grown into something that was hard to reason about and expensive to maintain - lots of administrative overhead just to keep it running, let alone extend it. Deploying the pipeline also took far too much time.&lt;/p&gt;&#10;&lt;p&gt;This project was a ground-up rebuild of that pipeline with the explicit goal of removing accumulated complexity and reducing the administrative burden of maintaining lab environments. Rather than patch the existing pipeline again, I rebuilt it with a cleaner, more streamlined deployment process - fewer special cases, more consistent conventions, and less manual intervention required to stand up or tear down a lab environment. The overall deployment time went from 45 minutes to less than 25 minutes.&lt;/p&gt;</description></item></channel></rss>