<?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 Alexander's Blog</title><link>https://alexanderbakin.com/tags/ci/cd/</link><description>Recent content in CI/CD on Alexander's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 21:15:35 +0400</lastBuildDate><atom:link href="https://alexanderbakin.com/tags/ci/cd/index.xml" rel="self" type="application/rss+xml"/><item><title>From 4 Hours to 20 Minutes: Replacing a Manual Deployment with GitLab CI</title><link>https://alexanderbakin.com/faster-gitlab-ci/</link><pubDate>Tue, 09 Apr 2024 00:00:00 +0000</pubDate><guid>https://alexanderbakin.com/faster-gitlab-ci/</guid><description>&lt;p&gt;Deploying used to mean an engineer, a runbook document, and four hours of undivided attention. Not four hours of a pipeline running in the background, four hours of a person actively driving it: SSH into the target host, pull the latest code, run the build script by hand, stop the old process, start the new one, watch the logs to see if it came up clean, and post a status update. It worked, in the sense that it got code to production. It didn&amp;rsquo;t scale, in the sense that &amp;ldquo;get code to production&amp;rdquo; now depended entirely on one specific person having a free afternoon.&lt;/p&gt;</description></item></channel></rss>