<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on Dagimal (⌐ ͡■ ͜ʖ ͡■)</title><link>https://dagimal.com/blog/automation/</link><description>Recent content in Automation on Dagimal (⌐ ͡■ ͜ʖ ͡■)</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2024, Dagimal.</copyright><lastBuildDate>Tue, 07 Apr 2026 11:45:00 +0700</lastBuildDate><atom:link href="https://dagimal.com/blog/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>CI/CD in a Nutshell: Deploy Otomatis Tanpa Repot</title><link>https://dagimal.com/blog/cicd-nutshell/</link><pubDate>Tue, 07 Apr 2026 11:45:00 +0700</pubDate><guid>https://dagimal.com/blog/cicd-nutshell/</guid><description>&lt;p&gt;Jadi, bayangkan dulu scenario ini: kita habis selesai coding feature baru, test lokal ternyata jalan, tapi pas di-push ke &lt;em&gt;production&lt;/em&gt; malah error. Kenapa? Karena &lt;em&gt;environment&lt;/em&gt; production beda, &lt;em&gt;dependency&lt;/em&gt; yang terinstall beda, atau kita lupa run &lt;em&gt;migration&lt;/em&gt; database. Panik deh.&lt;/p&gt;
&lt;p&gt;Nah, &lt;em&gt;CI/CD&lt;/em&gt; ini basically adalah cara kita mengotomatisasi supaya scenario kacau gitu gak terjadi. Daripada kita manually test, build, dan deploy (yang biasanya error-prone dan butuh effort besar), &lt;strong&gt;kita biarkan automation tools yang handle semuanya&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>