[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-rise-free-risc-v-github-runners-zh":3,"tags-rise-free-risc-v-github-runners-zh":33,"related-lang-rise-free-risc-v-github-runners-zh":47,"related-posts-rise-free-risc-v-github-runners-zh":51,"series-tools-fb4fa5cf-da7c-488c-b1be-0c2962f67696":88},{"id":4,"title":5,"content":6,"summary":7,"source":8,"source_url":9,"author":10,"image_url":11,"keywords":12,"language":21,"translated_content":10,"views":22,"is_premium":23,"created_at":24,"updated_at":24,"cover_image":11,"published_at":25,"rewrite_status":26,"rewrite_error":10,"rewritten_from_id":27,"slug":28,"category":29,"related_article_id":30,"status":31,"google_indexed_at":32,"x_posted_at":10,"tweet_text":10,"title_rewritten_at":10,"title_original":10,"key_takeaways":10,"topic_cluster_id":10,"embedding":10,"is_canonical_seed":23},"fb4fa5cf-da7c-488c-b1be-0c2962f67696","RISE 開放免費 RISC-V GitHub Runner","\u003Cp>RISC-V 這次真的有料。\u003Ca href=\"https:\u002F\u002Friscv.org\u002F\" target=\"_blank\" rel=\"noopener\">RISC-V\u003C\u002Fa> 的 \u003Ca href=\"https:\u002F\u002Friseproject.dev\u002F\" target=\"_blank\" rel=\"noopener\">RISE\u003C\u002Fa> 專案，現在開放免費 GitHub Runners。重點很直接：開源專案可以在真實 riscv64 硬體上跑 CI，不用只靠模擬器猜結果。\u003C\u002Fp>\u003Cp>這件事看起來小，實際上很痛。很多 \u003Ca href=\"\u002Fnews\u002Frvcc-llvm-incubator-riscv-optimizations-zh\">RISC\u003C\u002Fa>-V 專案不是沒人做。是\u003Ca href=\"\u002Fnews\u002Faime-2026-leaderboard-qwen-leads-math-tests-zh\">測試\u003C\u002Fa>太麻煩。板子要錢，機器要管，CI 還要穩。對志工型專案來說，這種成本很容易直接卡死。\u003C\u002Fp>\u003Cp>RISE 這次做的事很務實。它不是叫大家更愛 RISC-V。它是把最煩的那段拿掉。講白了，就是讓開源團隊少買一堆硬體，先把軟體跑起來。\u003C\u002Fp>\u003Ch2>RISE 到底提供什麼\u003C\u002Fh2>\u003Cp>RISE 提供的是管理好的 GitHub Actions runner。你把 workflow 指到 runner，裝好 GitHub App，就能把測試丟到真實 RISC-V 機器上跑。這比 QEMU 只看過場畫面，實際多了。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775179667841-fuz0.png\" alt=\"RISE 開放免費 RISC-V GitHub Runner\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>對開發者來說，這種差很多。很多 bug 只有在真機才會冒出來。像是時序問題、原子操作、某些 syscall 行為，模擬器不一定抓得到。你在 CI 先抓到，總比 release 之後才被使用者罵好。\u003C\u002Fp>\u003Cp>RISE 的公告也講得很白。這是 Early Avai\u003Ca href=\"\u002Fnews\u002Fclaude-code-leak-reveals-hidden-features-zh\">la\u003C\u002Fa>bility。也就是說，現在能用，但還在早期階段。這種服務最怕兩件事：排隊太久，或文件太爛。只要其中一個出事，大家又會回去用 QEMU。\u003C\u002Fp>\u003Cul>\u003Cli>服務型態：管理式 GitHub Actions runners\u003C\u002Fli>\u003Cli>硬體：真實 RISC-V 機器\u003C\u002Fli>\u003Cli>費用：開源專案免費\u003C\u002Fli>\u003Cli>用途：build、test、CI pipeline\u003C\u002Fli>\u003Cli>平台：目前只支援 GitHub\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>為什麼這對 RISC-V 很重要\u003C\u002Fh2>\u003Cp>RISC-V 的吸引力，在於 ISA 開放，而且授權很寬鬆。這讓晶片商、學界、硬體社群都能自己玩。\u003Ca href=\"https:\u002F\u002Fwww.sifive.com\u002F\" target=\"_blank\" rel=\"noopener\">SiFive\u003C\u002Fa> 這類公司做商用 IP，社群也能做開源板子。路線很多，但軟體支援常常跟不上。\u003C\u002Fp>\u003Cp>這就是老問題。硬體做出來，不代表生態就能跟上。沒有測試，維護者就不敢合併 patch。沒有穩定 CI，架構支援就會變成「有人有空再修」。這種狀況在 Linux 世界很常見，RISC-V 只是更明顯。\u003C\u002Fp>\u003Cp>RISE 由 \u003Ca href=\"https:\u002F\u002Fwww.linuxfoundation.org\u002F\" target=\"_blank\" rel=\"noopener\">Linux Foundation\u003C\u002Fa> 旗下推動。它的任務很像補洞。不是做晶片。不是做編譯器。它是把開源專案缺的那塊硬體測試資源補上。這種基礎建設，通常不帥，但很有用。\u003C\u002Fp>\u003Cul>\u003Cli>RISC-V 公開發展可追溯到 2014 年\u003C\u002Fli>\u003Cli>ISA 授權寬鬆，商用和開源都能用\u003C\u002Fli>\u003Cli>RISE 目標是補軟體生態缺口\u003C\u002Fli>\u003Cli>這次主打的是 CI 不是桌面體驗\u003C\u002Fli>\u003Cli>對 embedded 和 server 試驗都很實際\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>硬體測試一直是卡點\u003C\u002Fh2>\u003Cp>很多人以為架構支援卡在編譯器。其實不只。真正麻煩的是測試。你要有固定機器，要有可重現環境，還要有足夠吞吐量。沒有這些，CI 就只是跑個形式。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775179664180-1did.png\" alt=\"RISE 開放免費 RISC-V GitHub Runner\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>RISC-V 專案以前常見兩條路。第一條是 QEMU。便宜，但不一定準。第二條是自己買板子。準，但要錢、要維護、要備援。對小團隊來說，這兩條都不輕鬆。\u003C\u002Fp>\u003Cp>RISE 的 runner 服務，就是把這個成本拿走。它讓開源專案用真硬體跑 CI，卻不用自己養機器。這對 compiler、runtime、kernel module、low-level library 都很有感。因為這些東西最怕架構差異。\u003C\u002Fp>\u003Cblockquote>“Today, we are excited to announce the Early Availability of the RISE RISC-V Runners, a free, managed GitHub Actions runner service that gives any open source project access to real RISC-V hardware in their CI pipelines,” said Ludovic Henry.\u003C\u002Fblockquote>\u003Ch2>跟常見方案比，差在哪\u003C\u002Fh2>\u003Cp>如果你要驗證 riscv64 支援，通常有幾個選項。模擬器、cross-compilation、自架板子、共用實驗室資源。每一種都能用，但每一種都很煩。RISE 的價值，就是把其中最麻煩的硬體維護拿掉。\u003C\u002Fp>\u003Cp>先看模擬器。QEMU 很方便，啟動快，成本低。問題是它不等於真機。某些效能問題、記憶體行為、裝置互動，模擬器就是抓不準。你可以先過 build，但 runtime 還是會翻車。\u003C\u002Fp>\u003Cp>再看自架板子。這最貼近真實情況，但也最像在養家電。電源、網路、遠端重開、壞板更換，樣樣都要管。小專案通常沒這種人力。RISE 的 runner 直接省掉這些麻煩。\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>QEMU\u003C\u002Fstrong>：便宜快，但不一定準\u003C\u002Fli>\u003Cli>\u003Cstrong>Cross-compilation\u003C\u002Fstrong>：能驗 build，抓不到很多 runtime 問題\u003C\u002Fli>\u003Cli>\u003Cstrong>自架硬體\u003C\u002Fstrong>：最準，但維護成本高\u003C\u002Fli>\u003Cli>\u003Cstrong>RISE runners\u003C\u002Fstrong>：真硬體，且對開源專案免費\u003C\u002Fli>\u003C\u002Ful>\u003Cp>還有一個現實限制。現在只支援 GitHub。這表示 GitLab、Gitea、Bitbucket 的專案，暫時吃不到這波紅利。這點很可惜，但也合理。先把最大宗的開源工作流做好，比先喊全平台支援實在多了。\u003C\u002Fp>\u003Cp>如果你問我，這種服務最重要的不是「有沒有」。而是「穩不穩」。只要 runner 夠穩，隊列不長，大家就會慢慢把 riscv64 加進 CI。那時候，RISC-V 才真的比較像日常選項。\u003C\u002Fp>\u003Ch2>這波其實是生態補課\u003C\u002Fh2>\u003Cp>RISC-V 不是新名詞了。硬體圈講了很多年。問題一直都不是概念，而是落地。晶片、板子、工具鏈、套件、測試，這些東西要一起動，架構才會真的活起來。\u003C\u002Fp>\u003Cp>我覺得 RISE 這次做的，像是在幫開源社群補課。以前大家常說要支持新架構。現在它直接把門檻降低。你不用先買硬體，也能先把 CI 建起來。這對維護者很友善，對使用者也更安心。\u003C\u002Fp>\u003Cp>這類基礎設施很少上新聞，但影響很實際。當一個架構能被正常測試，套件維護者就比較敢合併 patch。等這件事變成習慣，RISC-V 才會從「特別支援」變成「預設支援」。\u003C\u002Fp>\u003Cp>接下來我會盯兩件事。第一，runner 配額夠不夠。第二，文件和申請流程順不順。這兩個如果都做好，更多開源專案就會開始把 riscv64 加進 CI。你如果有維護 GitHub 專案，而且碰 RISC-V，現在就值得去試看看。\u003C\u002Fp>","RISE 讓開源專案可在真實 RISC-V 硬體上跑 GitHub CI。這次直接解掉測試門檻，對 riscv64 專案很實際。","www.hackster.io","https:\u002F\u002Fwww.hackster.io\u002Fnews\u002Frise-launches-risc-v-github-runners-providing-ci-and-build-services-free-to-open-source-projects-559fa92fa713",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775179667841-fuz0.png",[13,14,15,16,17,18,19,20],"RISC-V","RISE","GitHub Runners","CI","開源專案","riscv64","GitHub Actions","真實硬體","zh",0,false,"2026-04-03T01:27:27.157914+00:00","2026-04-03T01:27:26.971+00:00","done","0fe98726-8e11-440b-b318-b77deeb10213","rise-free-risc-v-github-runners-zh","tools","6b09d971-3ca8-4e5e-a6fa-9c176b5b4892","published","2026-04-07T07:41:13.129+00:00",[34,36,38,40,42,44,45,46],{"name":16,"slug":35},"ci",{"name":13,"slug":37},"risc-v",{"name":14,"slug":39},"rise",{"name":19,"slug":41},"github-actions",{"name":15,"slug":43},"github-runners",{"name":18,"slug":18},{"name":20,"slug":20},{"name":17,"slug":17},{"id":30,"slug":48,"title":49,"language":50},"rise-free-risc-v-github-runners-en","RISE Adds Free RISC-V GitHub Runners","en",[52,58,64,70,76,82],{"id":53,"slug":54,"title":55,"cover_image":56,"image_url":56,"created_at":57,"category":29},"d058a76f-6548-4135-8970-f3a97f255446","why-gemini-api-pricing-is-cheaper-than-it-looks-zh","為什麼 Gemini API 定價其實比看起來更便宜","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778869845081-j4m7.png","2026-05-15T18:30:25.797639+00:00",{"id":59,"slug":60,"title":61,"cover_image":62,"image_url":62,"created_at":63,"category":29},"68e4be16-dc38-4524-a6ea-5ebe22a6c4fb","why-vidhub-huiyuan-hutong-bushi-quan-shebei-tongyong-zh","為什麼 VidHub 會員互通不是「買一次全設備通用」","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778789450987-advz.png","2026-05-14T20:10:24.048988+00:00",{"id":65,"slug":66,"title":67,"cover_image":68,"image_url":68,"created_at":69,"category":29},"7a1e174f-746b-4e82-a0e3-b2475ab39747","why-buns-zig-to-rust-experiment-is-right-zh","為什麼 Bun 的 Zig-to-Rust 實驗是對的","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778767879127-5dna.png","2026-05-14T14:10:26.886397+00:00",{"id":71,"slug":72,"title":73,"cover_image":74,"image_url":74,"created_at":75,"category":29},"e742fc73-5a65-4db3-ad17-88c99262ceb7","why-openai-api-pricing-is-product-strategy-zh","為什麼 OpenAI API 定價是產品策略，不是註腳","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778749859485-chvz.png","2026-05-14T09:10:26.003818+00:00",{"id":77,"slug":78,"title":79,"cover_image":80,"image_url":80,"created_at":81,"category":29},"c757c5d8-eda9-45dc-9020-4b002f4d6237","why-claude-code-prompt-design-beats-ide-copilots-zh","為什麼 Claude Code 的提示設計贏過 IDE Copilot","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778742645084-dao9.png","2026-05-14T07:10:29.371901+00:00",{"id":83,"slug":84,"title":85,"cover_image":86,"image_url":86,"created_at":87,"category":29},"4adef3ab-9f07-4970-91cf-77b8b581b348","why-databricks-model-serving-is-right-default-zh","為什麼 Databricks Model Serving 是生產推論的正確預設","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778692245329-a2wt.png","2026-05-13T17:10:30.659153+00:00",[89,94,99,104,109,114,119,124,129,134],{"id":90,"slug":91,"title":92,"created_at":93},"de769291-4574-4c46-a76d-772bd99e6ec9","googles-biggest-gemini-launches-in-2026-zh","Google 2026 最大 Gemini 盤點","2026-03-26T07:26:39.21072+00:00",{"id":95,"slug":96,"title":97,"created_at":98},"855cd52f-6fab-46cc-a7c1-42195e8a0de4","surepath-real-time-mcp-policy-controls-zh","SurePath 推出即時 MCP 政策控管","2026-03-26T07:57:40.77233+00:00",{"id":100,"slug":101,"title":102,"created_at":103},"9b19ab54-edef-4dbd-9ce4-a51e4bae4ebb","mcp-in-2026-the-ai-tool-layer-teams-use-zh","2026 年 MCP：團隊真的在用的 AI 工具層","2026-03-26T08:01:46.589694+00:00",{"id":105,"slug":106,"title":107,"created_at":108},"af9c46c3-7a28-410b-9f04-32b3de30a68c","prompting-in-2026-what-actually-works-zh","2026 提示工程，真正有用的是什麼","2026-03-26T08:08:12.453028+00:00",{"id":110,"slug":111,"title":112,"created_at":113},"05553086-6ed0-4758-81fd-6cab24b575e0","garry-tan-open-sources-claude-code-toolkit-zh","Garry Tan 開源 Claude Code 工具包","2026-03-26T08:26:20.068737+00:00",{"id":115,"slug":116,"title":117,"created_at":118},"042a73a2-18a2-433d-9e8f-9802b9559aac","github-ai-projects-to-watch-in-2026-zh","2026 必看 20 個 GitHub AI 專案","2026-03-26T08:28:09.619964+00:00",{"id":120,"slug":121,"title":122,"created_at":123},"a5f94120-ac0d-4483-9a8b-63590071ac6a","claude-code-vs-cursor-2026-zh","Claude Code 與 Cursor 深度對比：202…","2026-03-26T13:27:14.279193+00:00",{"id":125,"slug":126,"title":127,"created_at":128},"0975afa1-e0c7-4130-a20d-d890eaed995e","practical-github-guide-learning-ml-2026-zh","2026 機器學習入門 GitHub 實用指南","2026-03-27T01:16:49.712576+00:00",{"id":130,"slug":131,"title":132,"created_at":133},"bfdb467a-290f-4a80-b3a9-6f081afb6dff","aiml-2026-student-ai-ml-lab-repo-review-zh","AIML-2026：像課綱的學生實驗 Repo","2026-03-27T01:21:51.467798+00:00",{"id":135,"slug":136,"title":137,"created_at":138},"80cabc3e-09fc-4ff5-8f07-b8d68f5ae545","ai-trending-github-repos-and-research-feeds-zh","AI Trending：把 AI 資源收成一張表","2026-03-27T01:31:35.262183+00:00"]