https://ayyzenn.github.io/tags/devops/Recent content in Devops on ayyzennHugo -- 0.163.3en-usTue, 10 Feb 2026 00:00:00 +0000https://ayyzenn.github.io/posts/docker-pipeline-from-github/Tue, 10 Feb 2026 00:00:00 +0000https://ayyzenn.github.io/posts/docker-pipeline-from-github/<h2 id="what-i-built">What I Built</h2> <p>I wanted Jenkins to pull code from GitHub, build a Docker image, and run a container automatically. This post is the pipeline I put together for that.</p> <hr> <h2 id="goal-from-manual-to-automatic">Goal: From Manual to Automatic</h2> <p>Manually, we usually do this:</p> <ol> <li>Clone a GitHub repository</li> <li>Run <code>docker build</code></li> <li>Run <code>docker run</code></li> <li>Check the output</li> </ol> <p>With Jenkins, all of this happens <strong>automatically</strong> when the pipeline runs.</p> <p>You click <strong>Build Now</strong> (or trigger from GitHub), and Jenkins does the rest.</p>https://ayyzenn.github.io/posts/jenkins-on-arch-linux/Mon, 09 Feb 2026 00:00:00 +0000https://ayyzenn.github.io/posts/jenkins-on-arch-linux/<h2 id="why-i-wrote-this">Why I Wrote This</h2> <p>I run Arch Linux with i3 and wanted Jenkins locally for CI/CD experiments. This covers Java 21, the Jenkins install, a test job, and a GitHub pipeline — exactly what I ran on my machine.</p> <hr> <h2 id="1-what-is-jenkins-simple-explanation">1. What is Jenkins? (Simple Explanation)</h2> <p><strong>Jenkins is an automation server.</strong></p> <p>You can tell Jenkins to:</p> <ul> <li>Get your code (for example from GitHub)</li> <li>Run commands (build, test, scripts)</li> <li>Show you if things passed or failed</li> </ul> <p>Instead of you running commands manually every time, Jenkins does it <strong>automatically</strong>.</p>https://ayyzenn.github.io/posts/ansible_adv/Sat, 17 Jan 2026 00:00:00 +0000https://ayyzenn.github.io/posts/ansible_adv/<h2 id="why-this-post-exists">Why This Post Exists</h2> <p>After writing my <strong>first real Ansible playbook</strong>, I realized something:</p> <blockquote> <p>Installing software manually once is easy. Installing it <strong>correctly, repeatedly, and safely</strong> is not.</p> </blockquote> <p>So I decided to automate something <strong>real</strong> and <strong>useful</strong>:</p> <ul> <li>Install <strong>Docker Engine (official way)</strong></li> <li>Prepare an Ubuntu server to become a <strong>Kubernetes node</strong></li> <li>Do everything using <strong>Ansible</strong></li> <li>No SSH-ing into the server again and again</li> </ul> <p>This post documents that journey.</p> <hr> <h2 id="real-setup-same-as-before">Real Setup (Same as Before)</h2> <p>Nothing fancy. Just real machines.</p>https://ayyzenn.github.io/posts/ansible/Thu, 15 Jan 2026 00:00:00 +0000https://ayyzenn.github.io/posts/ansible/<h2 id="what-is-ansible-in-simple-words">What is Ansible? (In Simple Words)</h2> <p>Think of <strong>Ansible as a remote control for your servers</strong>.</p> <p>Instead of:</p> <ul> <li>SSH into server</li> <li>Run commands manually</li> <li>Forget what you changed</li> <li>Repeat the same steps again and again</li> </ul> <p>You tell Ansible:</p> <blockquote> <p>“Hey, I want this server to look <em>like this</em>.”</p> </blockquote> <p>And Ansible makes it happen — <strong>again and again</strong>, without breaking things.</p> <p>The best part?</p> <ul> <li>No agent needed</li> <li>Just SSH</li> <li>Simple YAML files</li> <li>Very human-readable</li> </ul> <hr> <h2 id="my-setup-real-world">My Setup (Real World)</h2> <p>This is exactly what I used:</p>