<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cicd-Pipeline on No Semicolons</title><link>https://nosemicolons.com/tags/cicd-pipeline/</link><description>Recent content in Cicd-Pipeline on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 07 Jun 2026 10:22:56 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/cicd-pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Deployment Pipeline: How to Ship Generated Code Without Manual QA</title><link>https://nosemicolons.com/posts/ai-code-generation-deployment-pipeline-automated-qa/</link><pubDate>Sun, 07 Jun 2026 10:22:56 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-deployment-pipeline-automated-qa/</guid><description>&lt;p>Ever shipped AI-generated code straight to production and held your breath? Yeah, me too. That queasy feeling when you&amp;rsquo;re not 100% sure what the AI cooked up is exactly what it should be doing in your production environment.&lt;/p>
&lt;p>The thing is, AI code generation has fundamentally changed how we think about deployment pipelines. Traditional CI/CD assumes humans wrote every line, with human reasoning behind every decision. But AI-generated code brings unique challenges: inconsistent patterns, subtle logic errors that pass basic tests, and the occasional &amp;ldquo;creative interpretation&amp;rdquo; of requirements that works but isn&amp;rsquo;t quite what you intended.&lt;/p></description></item></channel></rss>