<?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 blog@devops</title><link>https://blog.ziembiewicz.dev/tags/ci-cd/</link><description>Recent content in Ci-Cd on blog@devops</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 08 Sep 2026 13:20:04 +0200</lastBuildDate><atom:link href="https://blog.ziembiewicz.dev/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Blog in a DevOps pipelines way</title><link>https://blog.ziembiewicz.dev/posts/2026-09-08-blog-devops-way/</link><pubDate>Tue, 08 Sep 2026 13:20:04 +0200</pubDate><guid>https://blog.ziembiewicz.dev/posts/2026-09-08-blog-devops-way/</guid><description>&lt;p&gt;Setting up a blog is not an engineering achievement. Hugo renders Markdown, GitHub hosts the&#10;result, and you &lt;em&gt;are&lt;/em&gt;* done in an afternoon.&lt;/p&gt;&#10;&lt;p&gt;What makes it worth writing about is that the path from &lt;em&gt;a character typed in an editor&lt;/em&gt; to&#10;&lt;em&gt;bytes served from a CDN&lt;/em&gt; contains, in miniature, nearly everything a real deployment pipeline&#10;contains: a fast inner loop, a slow outer loop, a trust boundary where secrets must not cross,&#10;a build that has to be reproducible on a machine you have never seen, a set of permissions that&#10;should be exactly as wide as the job needs and no wider, and — at the very end — DNS and TLS,&#10;where the ordering of two clicks is a security control rather than a preference.&lt;/p&gt;</description></item></channel></rss>