# Cloud Build Recipes - Saving the Build Cache

DevFeed: [Cloud Build Recipes - Saving the Build Cache](<https://devfeed.tech/articles/cloud-build-recipes-saving-the-build-cache-30592.md>)

Original publisher: [Read original article](<https://ryanharter.com/blog/2019/02/cloud-build-recipes-saving-the-build-cache/>)

Published: 2019-02-15T20:13:00Z

Content type: tutorial

Language: en

Sources: [Blogs on Ryan Harter](<https://devfeed.tech/sources/blogs-on-ryan-harter.md>)

Topics: [Caching](<https://devfeed.tech/topics/caching.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [ci](<https://devfeed.tech/topics/ci.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [gradle](<https://devfeed.tech/tags/gradle.md>)

## AI overview

This tutorial explains how to speed up Google Cloud Build CI builds by caching dependencies between builds. It describes deploying cache builders, storing cache files in Google Cloud Storage, restoring the cache early in the build process, and choosing cache keys tied to the files that define the cached items.

## Source excerpt

When building development projects on your local workstation speed is important. A quick feedback cycle can mean the difference between a productive day of test driven development and a day filled with distraction. Your continuous integration environment is different. Since CI is responsible for preventing bad code from being merged and creating production releases, most people value precision over speed. That's why most CI environments utilise isolated build environments and always run all of the tests.