<?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 Netdata</title><link>https://www.netdata.cloud/tags/jenkins/</link><description>Recent content in Jenkins on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 05:09:03 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/jenkins/index.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins Declarative Pipeline: Parallelism Fixes</title><link>https://www.netdata.cloud/academy/jenkins-declarative-pipeline/</link><pubDate>Sun, 17 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/jenkins-declarative-pipeline/</guid><description>&lt;p&gt;You&amp;rsquo;ve embraced the power of Jenkins Declarative Pipelines, and now you&amp;rsquo;re looking to take the next step in CI/CD optimization: running stages in parallel. The promise is alluring—slashing your build times by running tests, linting, and security scans simultaneously. You eagerly refactor your &lt;code&gt;Jenkinsfile&lt;/code&gt;, commit the change, and watch your pipeline trigger. But instead of blazing-fast execution, your build gets stuck, silently hanging with no obvious error.&lt;/p&gt;&#10;&lt;p&gt;This frustrating scenario is often caused by two insidious problems: executor starvation and node label mismatch. While the &lt;code&gt;parallel&lt;/code&gt; step in Jenkins is incredibly powerful, using it naively can lead to deadlocked pipelines and misconfigured jobs that fail in subtle ways. Understanding how Jenkins allocates resources is the key to unlocking true parallelism without the headaches. This guide will walk you through these common pitfalls and provide the best practices to avoid them.&lt;/p&gt;</description></item><item><title>Jenkins Monitoring</title><link>https://www.netdata.cloud/monitoring-101/jenkins-monitoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/monitoring-101/jenkins-monitoring/</guid><description>&lt;h2 id="jenkins-monitoring"&gt;Jenkins Monitoring&lt;/h2&gt;&#10;&lt;h3 id="what-is-jenkins"&gt;What Is Jenkins?&lt;/h3&gt;&#10;&lt;p&gt;&lt;a href="https://www.jenkins.io/"&gt;Jenkins&lt;/a&gt; is an open-source automation server that is used to automate the process of building, testing, and deploying software. It is a continuous integration tool that enables developers to continually test and integrate their codebase. It supports a range of plugins for building and deploying applications.&lt;/p&gt;&#10;&lt;h3 id="monitoring-jenkins-with-netdata"&gt;Monitoring Jenkins With Netdata&lt;/h3&gt;&#10;&lt;p&gt;To effectively monitor Jenkins, Netdata employs a robust methodology using an openmetrics (Prometheus) exporter. This integration is seamless as Netdata can ingest data from any Prometheus exporter. It saves users from having to maintain separate Prometheus server and Grafana dashboard setups. With Netdata, automated dashboards and alerts become instantly accessible, providing real-time insights and alerting on critical metrics.&lt;/p&gt;</description></item></channel></rss>