<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Continuous Integration on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/continuous-integration/</link><description>Recent content in Continuous Integration on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 12 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/continuous-integration/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 3: Introduction to CI/CD - Automating Your Software Flow</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/introduction-ci-cd/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/introduction-ci-cd/</guid><description>&lt;h2 id="chapter-3-introduction-to-cicd---automating-your-software-flow"&gt;Chapter 3: Introduction to CI/CD - Automating Your Software Flow&lt;/h2&gt;
&lt;p&gt;Welcome back, future DevOps expert! In our previous chapters, we laid the groundwork by understanding the Linux command line and mastering version control with Git and GitHub. You now know how to manage code, track changes, and collaborate effectively. But what happens after you push your code to GitHub? How does it get built, tested, and eventually deployed to users?&lt;/p&gt;</description></item><item><title>Chapter 4: Building CI/CD with GitHub Actions</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/github-actions-ci-cd/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/github-actions-ci-cd/</guid><description>&lt;h2 id="introduction-to-continuous-integration--github-actions"&gt;Introduction to Continuous Integration &amp;amp; GitHub Actions&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 4! In our journey through DevOps, we&amp;rsquo;ve explored the foundational elements of Linux, command-line mastery, and the power of Git for version control. Now, it&amp;rsquo;s time to elevate our development process by introducing &lt;strong&gt;Continuous Integration (CI)&lt;/strong&gt; and &lt;strong&gt;Continuous Delivery (CD)&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;CI/CD is the backbone of modern software development. It&amp;rsquo;s about automating the build, test, and deployment phases of your application lifecycle, ensuring that your code is always in a releasable state. Imagine pushing a change, and automatically, your tests run, your application builds, and it&amp;rsquo;s ready to be deployed – that&amp;rsquo;s the magic of CI/CD! This automation drastically reduces manual errors, speeds up development cycles, and allows teams to deliver value faster and more reliably.&lt;/p&gt;</description></item><item><title>Chapter 8.2: Automating with CI/CD</title><link>https://ai-blog.noorshomelab.dev/flutter-latest-version-and-production-things-chapters/chapter-8-2-automating-ci-cd-slug/</link><pubDate>Sun, 23 Nov 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/flutter-latest-version-and-production-things-chapters/chapter-8-2-automating-ci-cd-slug/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the fast-paced world of mobile app development, ensuring consistent quality, rapid iteration, and reliable deployments is paramount. This is where Continuous Integration (CI) and Continuous Delivery/Deployment (CD) come into play. For Flutter applications, a robust CI/CD pipeline can significantly streamline the development workflow, reduce manual errors, and accelerate the time-to-market for new features and bug fixes.&lt;/p&gt;
&lt;p&gt;This chapter delves into the fundamentals of CI/CD, its immense benefits for Flutter projects (using the latest version practices), and practical steps to automate your build, test, and deployment processes. By the end, you&amp;rsquo;ll understand how to leverage modern CI/CD tools to achieve greater efficiency and reliability in your Flutter production pipeline.&lt;/p&gt;</description></item></channel></rss>