<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jenkins on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/jenkins/</link>
    <description>Recent content in Jenkins on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Tue, 30 Sep 2025 14:19:59 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/jenkins/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Monitoring Jenkins via Prometheus</title>
      <link>https://www.hairizuan.com/monitoring-jenkins-via-prometheus/</link>
      <pubDate>Mon, 25 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/monitoring-jenkins-via-prometheus/</guid>
      <description>&lt;p&gt;It is pretty important to understand how our jenkins job is running. We can technically keep querying the jenkins server via jenkins API but that would mean trying to parse the every changing response - which could be quite a painful process to go through. Instead, what we can do is to simply install 2 plugins - &lt;code&gt;metrics&lt;/code&gt; and &lt;code&gt;prometheus&lt;/code&gt; jenkins plugins.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Connect Slaves Jenkins configured with JCasC - Docker</title>
      <link>https://www.hairizuan.com/connect-slaves-jenkins-configured-with-jcasc-docker/</link>
      <pubDate>Wed, 10 Jan 2024 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/connect-slaves-jenkins-configured-with-jcasc-docker/</guid>
      <description>&lt;p&gt;This is a continuation of the previous blog post for automating Jenkins server setup. The previous setup only created a setup for a single node Jenkins build server farm. This definitely won&amp;rsquo;t be sufficient for larger teams where they would be building applications and running workflows on a more frequent basis. Refer to the page: &lt;a href=&#34;https://www.hairizuan.com/automating-jenkins-initial-setup&#34; &gt;Automating Jenkins Initial Setup&lt;/a&gt;&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Automating Jenkins Initial Setup</title>
      <link>https://www.hairizuan.com/automating-jenkins-initial-setup/</link>
      <pubDate>Wed, 03 Jan 2024 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/automating-jenkins-initial-setup/</guid>
      <description>&lt;p&gt;Jenkins, a pretty popular Continuous Integration/Continuous Deployment (CI/CD) build tool, plays a pivotal role in automating the software development/deployment process. Over the years, Jenkins has evolved to become an extremely versatile automation server that facilitates continuous integration and delivery by orchestrating the building, testing, and deployment of code. Its extensibility through a vast array of plugins makes it adaptable to various environments and development workflows.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
