<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci on Project Wintermute</title><link>https://wintermutecore.com/tags/ci/</link><description>Recent content in Ci on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 09 Jun 2026 14:56:14 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/ci/index.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins 2.567 Release: Fixing AJAX Widget Navigation Context</title><link>https://wintermutecore.com/posts/jenkins-2-567-release-ajax-widget-navigation-fix/</link><pubDate>Tue, 09 Jun 2026 14:56:14 +0000</pubDate><guid>https://wintermutecore.com/posts/jenkins-2-567-release-ajax-widget-navigation-fix/</guid><description>&lt;p&gt;The Jenkins project released version 2.567 on June 9, 2026, delivering a critical fix for navigation state within AJAX refreshed dashboard widgets. This update resolves a regression where links in the Build Queue and Build Executor Status sidebars would lose their view context during background updates. Operators relying on custom Jenkins views for monitoring complex build environments will find this release improves dashboard consistency and prevents broken navigation breadcrumbs.&lt;/p&gt;</description></item><item><title>Jenkins 2.566 Release: Improved Queue Performance and CSP Telemetry</title><link>https://wintermutecore.com/posts/jenkins-2-566-release-queue-performance-telemetry/</link><pubDate>Tue, 26 May 2026 07:50:27 +0000</pubDate><guid>https://wintermutecore.com/posts/jenkins-2-566-release-queue-performance-telemetry/</guid><description>&lt;p&gt;The Jenkins project released version 2.566 on May 26, 2026. This weekly release focuses on core runtime performance and security observability for the automation controller. The primary technical improvement addresses reflection overhead within the build queue maintenance logic, while new telemetry capabilities provide better insights into security policy enforcement.&lt;/p&gt;</description></item><item><title>Tag-based AWS resource cleanup: patterns that actually scale</title><link>https://wintermutecore.com/posts/aws-tag-based-resource-cleanup/</link><pubDate>Fri, 03 Apr 2026 11:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/aws-tag-based-resource-cleanup/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Name and time filters are not enough for safe AWS bulk cleanup. Use tags as the primary signal, expect &lt;code&gt;ListTagsForResource&lt;/code&gt; to be your bottleneck, enforce tagging at provisioning time, and run an audit job that flags untagged resources so the policy stays honest.&lt;/p&gt;
&lt;p&gt;The &amp;ldquo;delete a lot of AWS resources at once&amp;rdquo; problem shows up in every account: CI sandboxes, expired test estates, dev environments forgotten about, ad-hoc reproductions left behind. Bulk cleanup tools that target this exist and work well. Used carelessly any of them is a footgun. Used carefully with tag filtering, they become one of the most useful pieces of cost discipline you can ship.&lt;/p&gt;</description></item><item><title>Speeding up GitHub Actions lint pipelines for large Go codebases</title><link>https://wintermutecore.com/posts/go-ci-lint-pipeline-optimisation/</link><pubDate>Thu, 12 Feb 2026 10:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/go-ci-lint-pipeline-optimisation/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Lint on a large Go monorepo went from 63 seconds to about 25 seconds on warm cache, with macOS skipped on branches. Five changes: concurrency group, conditional OS matrix, combined cache restore and save, explicit &lt;code&gt;go mod download&lt;/code&gt;, and incremental &lt;code&gt;golangci-lint --new-from-rev&lt;/code&gt;. None require a self-hosted runner.&lt;/p&gt;
&lt;p&gt;A large Go codebase makes the CI lint stage the part developers feel most: every push, on every branch. Lint feedback that takes a minute and a half kills iteration speed and quietly trains people to push less often, which is the opposite of what you want.&lt;/p&gt;</description></item></channel></rss>