<?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 on martinuke0&#39;s Blog</title>
    <link>https://martinuke0.github.io/tags/ci/</link>
    <description>Recent content in Ci on martinuke0&#39;s Blog</description>
    <image>
      <title>martinuke0&#39;s Blog</title>
      <url>https://martinuke0.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://martinuke0.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <lastBuildDate>Fri, 18 Sep 2026 18:02:29 +0000</lastBuildDate>
    <atom:link href="https://martinuke0.github.io/tags/ci/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tekton, Argo, and GitHub Actions: A Deep Dive into Modern CI/CD Pipelines</title>
      <link>https://martinuke0.github.io/posts/2026-09-18-tekton-argo-and-github-actions-a-deep-dive-into-modern-cicd-pipelines/</link>
      <pubDate>Fri, 18 Sep 2026 18:02:29 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-09-18-tekton-argo-and-github-actions-a-deep-dive-into-modern-cicd-pipelines/</guid>
      <description>A comprehensive comparison of Tekton, Argo, and GitHub Actions — three leading CI/CD platforms — examining their architecture, strengths, and ideal use cases for engineering teams.</description>
    </item>
    <item>
      <title>Deep Dive into Buildkite Test Analytics for Flaky Test Triage</title>
      <link>https://martinuke0.github.io/posts/2026-09-12-deep-dive-into-buildkite-test-analytics-for-flaky-test-triage/</link>
      <pubDate>Sat, 12 Sep 2026 06:01:31 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-09-12-deep-dive-into-buildkite-test-analytics-for-flaky-test-triage/</guid>
      <description>Learn how Buildkite Test Analytics helps identify and prioritize flaky tests, reducing CI noise and accelerating release cycles for engineering teams.</description>
    </item>
    <item>
      <title>Architecting the Modern Software Factory: Designing Specialized Agent Workflows for Production-Ready Development Pipelines</title>
      <link>https://martinuke0.github.io/posts/2026-05-24-architecting-the-modern-software-factory-designing-specialized-agent-workflows-for-production-ready-development-pipelines/</link>
      <pubDate>Sun, 24 May 2026 10:00:52 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-05-24-architecting-the-modern-software-factory-designing-specialized-agent-workflows-for-production-ready-development-pipelines/</guid>
      <description>Learn how to build production‑ready pipelines with specialized AI agents, focusing on architecture, patterns, and implementations on Kafka, Airflow, and GCP.</description>
    </item>
    <item>
      <title>Mastering Ephemeral Environments with CCR, GitHub Actions, and SDKs</title>
      <link>https://martinuke0.github.io/posts/2026-03-31-mastering-ephemeral-environments-with-ccr-github-actions-and-sdks/</link>
      <pubDate>Tue, 31 Mar 2026 16:12:09 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-03-31-mastering-ephemeral-environments-with-ccr-github-actions-and-sdks/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Modern software delivery demands speed, reliability, and reproducibility. Traditional monolithic test and staging environments often become bottlenecks: they are expensive to maintain, prone to configuration drift, and can hide integration issues until the very last stages of a release pipeline.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Ephemeral environments&lt;/strong&gt;—short‑lived, on‑demand instances of an application stack—offer a compelling alternative. By provisioning a fresh copy of the entire system for each pull request, feature branch, or even a single test case, teams gain:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building Autonomous Development Pipelines with Cursor and Advanced Batch Processing Workflows</title>
      <link>https://martinuke0.github.io/posts/2026-03-28-building-autonomous-development-pipelines-with-cursor-and-advanced-batch-processing-workflows/</link>
      <pubDate>Sat, 28 Mar 2026 08:00:49 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-03-28-building-autonomous-development-pipelines-with-cursor-and-advanced-batch-processing-workflows/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The modern software development landscape demands speed, reliability, and repeatability. Teams that can ship changes multiple times a day while maintaining high quality gain a decisive competitive edge. Achieving this level of agility typically requires &lt;strong&gt;autonomous development pipelines&lt;/strong&gt;—systems that can generate, test, and deploy code with minimal human intervention.&lt;/p&gt;
&lt;p&gt;Enter &lt;strong&gt;Cursor&lt;/strong&gt;, an AI‑driven code assistant that can understand natural language, write production‑ready snippets, refactor existing code, and even suggest architectural improvements. When paired with &lt;strong&gt;advanced batch processing workflows&lt;/strong&gt; (e.g., Apache Airflow, AWS Batch, or custom Python orchestrators), Cursor becomes a catalyst for building pipelines that not only compile and test code but also &lt;strong&gt;generate new code on the fly&lt;/strong&gt;, adapt to changing requirements, and process large‑scale data transformations.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mastering Infrastructure as Code for Scaling Cloud Native Applications From Development to Production</title>
      <link>https://martinuke0.github.io/posts/2026-03-12-mastering-infrastructure-as-code-for-scaling-cloud-native-applications-from-development-to-production/</link>
      <pubDate>Thu, 12 Mar 2026 01:01:01 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-03-12-mastering-infrastructure-as-code-for-scaling-cloud-native-applications-from-development-to-production/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Infrastructure as Code (IaC) has moved from a niche practice to a cornerstone of modern software delivery. When building cloud‑native applications that must scale from a single developer’s laptop to a globally distributed production environment, the ability to &lt;strong&gt;declare&lt;/strong&gt;, &lt;strong&gt;version&lt;/strong&gt;, and &lt;strong&gt;automate&lt;/strong&gt; every piece of infrastructure is no longer optional—it’s a competitive necessity.&lt;/p&gt;
&lt;p&gt;In this article we will:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Explain why IaC is essential for scaling cloud‑native workloads.&lt;/li&gt;
&lt;li&gt;Walk through the complete lifecycle—from local development environments to production‑grade clusters.&lt;/li&gt;
&lt;li&gt;Compare the most widely‑used IaC tools and show how to choose the right one for your stack.&lt;/li&gt;
&lt;li&gt;Provide hands‑on, production‑ready code examples using Terraform, Pulumi, and Kubernetes manifests.&lt;/li&gt;
&lt;li&gt;Discuss best‑practice patterns for testing, security, and continuous delivery.&lt;/li&gt;
&lt;li&gt;Tie everything together with a practical, end‑to‑end case study.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;By the end of this guide you’ll have a concrete roadmap to &lt;strong&gt;master IaC&lt;/strong&gt;, reduce manual toil, and confidently scale your applications across any cloud provider.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GitHub Actions: From Zero to Hero - A Complete Tutorial</title>
      <link>https://martinuke0.github.io/posts/github-actions-tutorial/</link>
      <pubDate>Thu, 27 Nov 2025 13:38:00 +0200</pubDate>
      <guid>https://martinuke0.github.io/posts/github-actions-tutorial/</guid>
      <description>&lt;p&gt;GitHub Actions is like having a robot assistant that automatically does tasks for you whenever something happens in your GitHub repository. This tutorial will take you from complete beginner to advanced user, putting you ahead of 90% of developers.&lt;/p&gt;
&lt;h3 id=&#34;table-of-contents&#34;&gt;Table of Contents&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&#34;#what-is-github-actions-eli5&#34;&gt;What is GitHub Actions? (ELI5)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#core-concepts&#34;&gt;Core Concepts&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#your-first-workflow&#34;&gt;Your First Workflow&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#intermediate-techniques&#34;&gt;Intermediate Techniques&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#advanced-patterns&#34;&gt;Advanced Patterns&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#real-world-examples&#34;&gt;Real-World Examples&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#pro-tips--best-practices&#34;&gt;Pro Tips &amp;amp; Best Practices&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#useful-resources&#34;&gt;Useful Resources&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h3 id=&#34;what-is-github-actions-eli5&#34;&gt;What is GitHub Actions? (ELI5)&lt;/h3&gt;
&lt;p&gt;Imagine you have a lemonade stand. Every time you make lemonade, you need to:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
