<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cicd on Romi's Dev Journey</title><link>https://romisugi.dev/tags/cicd/</link><description>Recent content in Cicd on Romi's Dev Journey</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 24 Sep 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://romisugi.dev/tags/cicd/index.xml" rel="self" type="application/rss+xml"/><item><title>Simplifying Legacy App Deployment with rsync Backup Magic</title><link>https://romisugi.dev/posts/devops-tips/rsync-backup-deployment/</link><pubDate>Wed, 24 Sep 2025 00:00:00 +0000</pubDate><guid>https://romisugi.dev/posts/devops-tips/rsync-backup-deployment/</guid><description>&lt;h2 id="the-pain-of-legacy-deployment">The Pain of Legacy Deployment&lt;/h2>
&lt;p>So lately I&amp;rsquo;ve been working on another Jenkins pipeline, and there&amp;rsquo;s this service - a scheduler that still runs vanilla style on traditional VMs without containers. Despite many reasons I can&amp;rsquo;t win that containerization fight yet, I needed to make this vanilla app deployment at least a bit more bearable with CI/CD.&lt;/p>
&lt;p>This scheduler is a JAR file with its dependencies, updated regularly. But the deployment flow? Pure torture. I had to copy files one by one, backup one by one. I know if I could just get permission to containerize this thing, the suffering would end. But work must go on.&lt;/p></description></item></channel></rss>