<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pipeline on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pipeline/</link>
    <description>Recent content in Pipeline on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pipeline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GoCD vs Buildbot vs Jenkins: Self-Hosted CI/CD Dashboard Comparison 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-05-gocd-vs-buildbot-vs-jenkins-self-hosted-cicd-dashboard-guide/</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-05-gocd-vs-buildbot-vs-jenkins-self-hosted-cicd-dashboard-guide/</guid>
      <description>&lt;p&gt;A continuous integration and delivery pipeline is only as useful as your ability to see what it is doing. When you have dozens of jobs running across multiple repositories, a clear dashboard becomes the operational nerve center — showing build status, deployment progress, test failures, and environment health at a glance. While many CI/CD platforms include built-in status pages, dedicated CI/CD dashboards offer richer visualization, multi-pipeline aggregation, and team-wide visibility.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
