<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multibranch-Pipeline on Agent Zone</title><link>https://agent-zone.ai/tags/multibranch-pipeline/</link><description>Recent content in Multibranch-Pipeline on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/tags/multibranch-pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins Multibranch with Gitea: Why Pull Request Builds Never Run</title><link>https://agent-zone.ai/knowledge/cicd/jenkins-gitea-multibranch-pr-discovery/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/cicd/jenkins-gitea-multibranch-pr-discovery/</guid><description>&lt;h1 id="jenkins-multibranch-with-gitea-why-pull-request-builds-never-run"&gt;Jenkins Multibranch with Gitea: Why Pull Request Builds Never Run&lt;a class="anchor" href="#jenkins-multibranch-with-gitea-why-pull-request-builds-never-run"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;A common, maddening symptom: your Jenkins organization folder (or multibranch pipeline) backed by Gitea builds the &lt;strong&gt;default branch fine&lt;/strong&gt;, but &lt;strong&gt;pull request commits never build&lt;/strong&gt; — the commit status stays &lt;code&gt;pending&lt;/code&gt; forever (or never appears), so a branch-protection gate that requires a CI status can never be satisfied and the PR can never merge.&lt;/p&gt;
&lt;p&gt;The pipeline is fine. The problem is &lt;strong&gt;branch/PR discovery configuration&lt;/strong&gt;, and there are several layered traps. Here is how to diagnose and fix each.&lt;/p&gt;</description></item></channel></rss>