<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Firecracker on nanmu42</title><link>https://nanmu.me/en/tags/firecracker/</link><description>Recent content in Firecracker on nanmu42</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>i@nanmu.me (nanmu42)</managingEditor><webMaster>i@nanmu.me (nanmu42)</webMaster><copyright>Copyright &amp;copy;{year} LI Zhennan</copyright><lastBuildDate>Thu, 29 Dec 2022 13:14:15 +0800</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><sy:updateFrequency>weekly</sy:updateFrequency><atom:link href="https://nanmu.me/en/tags/firecracker/index.xml" rel="self" type="application/rss+xml"/><item><title>Bring Your "Own" Gitlab CI Runner</title><link>https://nanmu.me/en/posts/2022/bring-your-own-gitlab-runner/</link><pubDate>Thu, 29 Dec 2022 13:14:15 +0800</pubDate><author>i@nanmu.me (nanmu42)</author><atom:modified>Tue, 06 Aug 2024 10:39:07 +0800</atom:modified><guid>https://nanmu.me/en/posts/2022/bring-your-own-gitlab-runner/</guid><description>Gitlab boasts this nifty feature of using your own Gitlab CI Runner. But what if you&amp;rsquo;re sans a &amp;ldquo;really personal&amp;rdquo; CI Runner? Fear not, we&amp;rsquo;re about to roll up our sleeves and craft one ourselves. []~(￣▽￣)~*
Our DIY Runner&amp;#39;s logo, feels like the project just got serious, right? In this dive, we&amp;rsquo;re going to:
Outline the core duties of a Gitlab Runner; Dissect the interactions between a Runner and Gitlab during operation; Design and implement our very own Runner; Bootstrap: get our Runner to run its own CI jobs.</description><dc:creator>nanmu42</dc:creator><category>Gitlab</category><category>Firecracker</category><category>Notes and Discussions</category></item></channel></rss>