<?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 dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/continuous-integration/</link>
		<description>Recent content in Continuous-Integration on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 25 Nov 2024 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/continuous-integration/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>CI/CD Is a Feedback Loop, Not a Deployment Tool</title>
				<link>https://dplabs.tech/blog/cicd-is-a-feedback-loop/</link>
				<pubDate>Mon, 25 Nov 2024 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/cicd-is-a-feedback-loop/</guid>
				<description>&lt;p&gt;Most CI/CD implementations optimize for the wrong thing. They treat the pipeline as a deployment automation tool — a mechanism for running tests and pushing artifacts to production. The tests pass, the deploy runs, work is done.&lt;/p&gt;&#xA;&lt;p&gt;This framing misses the fundamental value of continuous integration and continuous delivery: &lt;strong&gt;compressing the feedback loop between writing code and understanding its consequences&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The faster that loop runs, the faster defects are caught, the smaller the blast radius of errors, and the more confidence engineers have when deploying. Everything else follows from this.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
