<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI/CD on Kaisekukun</title><link>https://netguide.jp/zh-tw/tags/cicd/</link><description>Recent content in CI/CD on Kaisekukun</description><generator>Hugo -- gohugo.io</generator><language>zh-TW</language><copyright>Kaisekukun</copyright><atom:link href="https://netguide.jp/zh-tw/tags/cicd/index.xml" rel="self" type="application/rss+xml"/><item><title>Accelerating GitHub Actions CI/CD workflows using Caching</title><link>https://netguide.jp/zh-tw/software/github-actions-cicd-caching/</link><pubDate>Wed, 15 Apr 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/zh-tw/software/github-actions-cicd-caching/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/github-actions-cicd-caching-zh-tw.png" alt="Featured image of post Accelerating GitHub Actions CI/CD workflows using Caching" /&gt;&lt;p&gt;Optimizing CI/CD workflow times directly impacts developer productivity and reduces computing expenses. This article shows you how to integrate dependency caching in GitHub Actions, helping you slash compilation and package setup times.&lt;/p&gt;
&lt;p&gt;We provide YAML workflow templates for Node.js, Python, and Rust, alongside best practices to ensure optimal cache hits.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-why-cache-dependencies-in-cicd"&gt;1. Why Cache Dependencies in CI/CD?
&lt;/h2&gt;&lt;p&gt;When a CI agent starts without caching, it spins up a clean container and fetches every dependency from package registries. This introduces several drawbacks:&lt;/p&gt;</description></item><item><title>Getting Started with CI/CD Using GitHub Actions</title><link>https://netguide.jp/zh-tw/software/github-actions-ci-cd-basics/</link><pubDate>Tue, 06 Jan 2026 11:00:00 +0900</pubDate><guid>https://netguide.jp/zh-tw/software/github-actions-ci-cd-basics/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/github-actions-ci-cd-basics-zh-tw.png" alt="Featured image of post Getting Started with CI/CD Using GitHub Actions" /&gt;&lt;p&gt;If &amp;ldquo;CI/CD&amp;rdquo; sounds like something you should know but don&amp;rsquo;t know where to start, this guide is for you. &lt;strong&gt;GitHub Actions&lt;/strong&gt; makes continuous integration and delivery accessible to everyone with a GitHub repository.&lt;/p&gt;
&lt;h2 id="what-is-github-actions"&gt;What is GitHub Actions?
&lt;/h2&gt;&lt;p&gt;GitHub Actions is a CI/CD platform built directly into GitHub. It lets you automate testing, building, and deploying right from your repository. Workflows trigger on pushes, pull requests, or scheduled events.&lt;/p&gt;
&lt;h2 id="1-workflow-basics"&gt;1. Workflow Basics
&lt;/h2&gt;&lt;p&gt;Place a YAML file inside &lt;code&gt;.github/workflows/&lt;/code&gt; to define your workflow.&lt;/p&gt;</description></item></channel></rss>