<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scm-Polling on Agent Zone</title><link>https://agent-zone.ai/tags/scm-polling/</link><description>Recent content in Scm-Polling on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/tags/scm-polling/index.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins Multibranch Silent Skip After Branch Recreate: Rename to Recover</title><link>https://agent-zone.ai/knowledge/cicd/jenkins-multibranch-silent-skip/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/cicd/jenkins-multibranch-silent-skip/</guid><description>&lt;h1 id="jenkins-multibranch-silent-skip-after-branch-recreate"&gt;Jenkins Multibranch Silent Skip After Branch Recreate&lt;a class="anchor" href="#jenkins-multibranch-silent-skip-after-branch-recreate"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Push a branch named &lt;code&gt;fix/foo&lt;/code&gt;. Trigger a multibranch scan. The scan log shows &lt;code&gt;Checking branch fix/foo&lt;/code&gt; and immediately moves to the next branch with no verdict line. No job appears under the multibranch. No build fires. Other branches scan and build normally.&lt;/p&gt;
&lt;p&gt;This is Jenkins&amp;rsquo;s branch source plugin silently skipping a branch because its internal cache treats the name as a duplicate of a previously-deleted entry. The cache survives plugin restarts, multibranch rescans, and &lt;code&gt;kubectl rollout restart jenkins&lt;/code&gt;. The reliable recovery is to push the same commits under a different branch name — the cache has no entry for the new name and processes it cleanly.&lt;/p&gt;</description></item></channel></rss>