<?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 Notes from running platforms</title><link>https://fromnovid.com/tags/jenkins/</link><description>Recent content in Jenkins on Notes from running platforms</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://fromnovid.com/tags/jenkins/index.xml" rel="self" type="application/rss+xml"/><item><title>How one webhook URL stopped Bitbucket's 429s</title><link>https://fromnovid.com/posts/jenkins-bitbucket-429/</link><pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate><guid>https://fromnovid.com/posts/jenkins-bitbucket-429/</guid><description>&lt;p&gt;Jenkins kept crashing at peak hours. Nobody could deploy. Bitbucket answered with 429, rate limit exceeded. Bitbucket Cloud gives you 1000 API calls per hour, and we were burning through them before lunch.&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;HTTP/1.1 429 Too Many Requests&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The proposal on the table was to reduce the number of branches. Nobody had asked why one push turned into hundreds of API calls.&lt;/p&gt;</description></item></channel></rss>