<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci-Cd on Pi Stack</title><link>https://www.pistack.xyz/tags/ci-cd/</link><description>Recent content in Ci-Cd on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>JaCoCo vs Coverage.py vs Istanbul/nyc: Self-Hosted Code Coverage Guide 2026</title><link>https://www.pistack.xyz/posts/self-hosted-code-coverage-tools-jacoco-coverage-istanbul-guide-2026/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-code-coverage-tools-jacoco-coverage-istanbul-guide-2026/</guid><description>&lt;p>Code coverage is one of the most widely tracked software quality metrics. Knowing which lines, branches, and functions your tests exercise gives teams confidence when shipping changes. But sending coverage reports to cloud SaaS platforms like Codecov, Coveralls, or SonarCloud means handing your proprietary source metrics to a third party.&lt;/p></description></item><item><title>Tekton vs Argo Workflows vs Jenkins X: Kubernetes-Native CI/CD Guide 2026</title><link>https://www.pistack.xyz/posts/tekton-vs-argo-workflows-vs-jenkins-x-self-hosted-kubernetes-native-cicd-guide-2026/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/tekton-vs-argo-workflows-vs-jenkins-x-self-hosted-kubernetes-native-cicd-guide-2026/</guid><description>&lt;p>When your infrastructure runs on &lt;a href="https://kubernetes.io/">kubernetes&lt;/a>, running your build pipelines on anything else introduces unnecessary com&lt;a href="https://www.plex.tv/">plex&lt;/a>ity. Traditional CI/CD systems like Jenkins or GitLab CI were designed for VM-era infrastructure — they manage their own agents, build queues, and storage outside of your cluster. Kubernetes-native pipelines eliminate that gap by treating builds as first-class cluster resources.&lt;/p></description></item><item><title>Renovate vs Dependabot vs Updatecli: Self-Hosted Dependency Automation Guide 2026</title><link>https://www.pistack.xyz/posts/2026-04-19-renovate-vs-dependabot-vs-updatecli-self-hosted-dependency-automation-guide-2026/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-19-renovate-vs-dependabot-vs-updatecli-self-hosted-dependency-automation-guide-2026/</guid><description>&lt;p>Keeping dependencies up to date is one of the most tedious yet critical tasks in software development. Outdated packages introduce security vulnerabilities, miss performance improvements, and create technical debt that compounds over time. Manual dependency updates are error-prone and don&amp;rsquo;t scale across teams with dozens of repositories.&lt;/p></description></item><item><title>Woodpecker CI vs Drone CI vs Gitea Actions: Self-Hosted CI/CD Guide 2026</title><link>https://www.pistack.xyz/posts/2026-04-19-woodpecker-ci-vs-drone-ci-vs-gitea-actions-self-hosted-cicd-guide-2026/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-19-woodpecker-ci-vs-drone-ci-vs-gitea-actions-self-hosted-cicd-guide-2026/</guid><description>&lt;p>Self-hosted CI/CD platforms give you full control over your build infrastructure, pipeline execution, and artifact storage. When you can&amp;rsquo;t (or don&amp;rsquo;t want to) rely on cloud services like GitHub Actions, GitLab CI, or CircleCI, open-source alternatives let you run pipelines on your own servers with no usage limits or data leaving your infrastructure.&lt;/p></description></item><item><title>GitHub Actions Runner vs GitLab Runner vs Woodpecker: Self-Hosted CI Agents 2026</title><link>https://www.pistack.xyz/posts/github-actions-runner-vs-gitlab-runner-vs-woodpecker-self-hosted-ci-agents-2026/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/github-actions-runner-vs-gitlab-runner-vs-woodpecker-self-hosted-ci-agents-2026/</guid><description>&lt;p>Running CI/CD pipelines on shared cloud infrastructure means your build logs, source code, and artifacts pass through servers you don&amp;rsquo;t control. For teams handling proprietary code, compliance-sensitive workloads, or simply wanting faster builds on local hardware, self-hosted CI runners are the answer. This guide compares the three most popular self-hosted CI execution agents: &lt;strong>GitHub Actions Runner&lt;/strong>, &lt;strong>GitLab Runner&lt;/strong>, and &lt;strong>Woodpecker CI&lt;/strong> — covering architecture, &lt;a href="https://www.docker.com/">docker&lt;/a> deployment, configuration, and when to choose each one.&lt;/p></description></item><item><title>Pa11y vs Lighthouse CI vs axe-core: Best Self-Hosted Accessibility Testing 2026</title><link>https://www.pistack.xyz/posts/2026-04-18-self-hosted-web-accessibility-testing-pa11y-lighthouse-ci-axe-core-guide-2026/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-18-self-hosted-web-accessibility-testing-pa11y-lighthouse-ci-axe-core-guide-2026/</guid><description>&lt;p>Web accessibility is no longer optional. With the European Accessibility Act taking effect in 2025 and lawsuits increasing worldwide, every public-facing website must meet WCAG 2.2 AA standards. Automated accessibility testing catches 30-50% of compliance issues before they reach production — but commercial platforms like Siteimprove and Deque University charge hundreds of dollars per month.&lt;/p></description></item></channel></rss>