<?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 toorun.dev</title><link>https://toorun.dev/tags/ci-cd/</link><description>Recent content in ci-cd on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 06:30:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins Configuration as Code (JCasC): From Manual Setup to Reproducible Infrastructure</title><link>https://toorun.dev/posts/jenkins-configuration-as-code-jcasc-from-manual-setup-to-reproducible-infrastructure/</link><pubDate>Sun, 10 May 2026 06:30:00 +0000</pubDate><guid>https://toorun.dev/posts/jenkins-configuration-as-code-jcasc-from-manual-setup-to-reproducible-infrastructure/</guid><description>The Problem: Manual Jenkins Configuration is a Nightmare If you&amp;rsquo;ve managed Jenkins for any length of time, you know the pain. A new server crashes, and you need to:
Recreate users and permissions Reinstall plugins Reconfigure security settings Rebuild all your job definitions Hope you remember which obscure checkbox you clicked last time Then you get to explain to your team why everything is down because nobody documented how the &amp;ldquo;old&amp;rdquo; Jenkins was set up.</description></item></channel></rss>