<?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 Ajay Dhungel</title>
    <link>/tags/cicd/</link>
    <description>Recent content in Cicd on Ajay Dhungel</description>
    <generator>Hugo 0.125.0</generator>
    <language>en</language>
    <copyright>DevOps Engineer | Cloud Infrastructure | AWS</copyright>
    <lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/cicd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I Built a Portfolio Site That Updates Itself Every Night</title>
      <link>/posts/automated-portfolio/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/automated-portfolio/</guid>
      <description>The Problem with Portfolio Sites I had let mine go stale for months. I&amp;rsquo;d shipped projects, written posts, earned certifications, and none of it showed up because updating the site meant carving out time I never had. At some point I stopped pretending discipline was the answer and just automated the whole thing.&#xA;This post covers how I wired four external data sources into a Hugo site that updates itself nightly, with a CI/CD pipeline that tests, builds, and deploys without me touching anything.</description>
    </item>
    <item>
      <title>Build Once, Promote Everywhere: GitHub Actions the Right Way</title>
      <link>/posts/github-actions-image-promotion/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/github-actions-image-promotion/</guid>
      <description>Introduction Something I see a lot in CI/CD setups is a separate pipeline for each environment, each one building its own Docker image. Dev pipeline builds an image, staging pipeline builds an image, production pipeline builds an image. The code is the same. The Dockerfile is the same. The result is theoretically the same. But you spent three build cycles to get there, and you have no actual guarantee that what you tested in dev is what you shipped to prod.</description>
    </item>
  </channel>
</rss>
