<?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>Cache on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/cache/</link><description>Recent content in Cache on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Tue, 22 Feb 2022 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/cache/atom.xml" rel="self" type="application/rss+xml"/><item><title>How Staged Builds Cache Third-Party Dependencies</title><link>https://www.chenshaowen.com/en/blog/how-to-cache-third-party-package-whilie-building-in-stage.html</link><pubDate>Tue, 22 Feb 2022 00:00:00 +0000</pubDate><atom:modified>Tue, 22 Feb 2022 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-to-cache-third-party-package-whilie-building-in-stage.html</guid><description>In a non-staged build scenario, when we use a container to build, we can mount the cache directory inside the container onto the build host, run the build task, and then copy the artifacts into the runtime image to produce the application image. But with a staged build, the build image and the runtime image live in the same Dockerfile, which makes it harder to optimize the caching of third-party dependencies.</description><dc:creator>微信公众号</dc:creator><category>CICD</category><category>CI</category><category>DevOps</category><category>Cache</category><category>Optimization</category></item><item><title>Build Artifacts and Cache in Jenkins</title><link>https://www.chenshaowen.com/en/blog/artifacts-and-cache-in-jenkins.html</link><pubDate>Sun, 21 Jun 2020 00:00:00 +0000</pubDate><atom:modified>Sun, 21 Jun 2020 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/artifacts-and-cache-in-jenkins.html</guid><description>In a CICD flow, there are two main kinds of things that need to be saved: build artifacts and caches. Build artifacts are the final execution result, and caches exist to speed up the next build. This post mainly describes how to archive build artifacts and caches in Jenkins, along with a hands-on example backed by object storage.</description><dc:creator>微信公众号</dc:creator><category>Jenkins</category><category>S3</category><category>DevOps</category><category>Cache</category></item></channel></rss>