<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Runner on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/runner/</link><description>Recent content in Runner on SRE Engineering Practice</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 13 Aug 2026 10:35:41 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/runner/index.xml" rel="self" type="application/rss+xml"/><item><title>Starting from Docker Machine Deprecation: 7 Production Decisions for GitLab CI Runner Elastic Architecture and Cache Governance</title><link>https://www.sre.wang/en/posts/cicd-gitlab-runner-autoscaling-cache/</link><pubDate>Thu, 13 Aug 2026 10:35:41 +0800</pubDate><guid>https://www.sre.wang/en/posts/cicd-gitlab-runner-autoscaling-cache/</guid><description>GitLab 17.5 deprecated the Docker Machine executor, with full removal planned for 2027. This article breaks down 7 engineering decisions for scaling GitLab CI from 50 to 200 concurrent jobs, covering executor selection, Kubernetes Executor resource modeling, distributed cache design, and production pitfalls.</description></item></channel></rss>