简体   繁体   English

Google Cloud Build不缓存自定义构建步骤?

[英]Google Cloud Build not caching custom build steps?

Is it possible to have Google Cloud Build cache custom build step images? 是否可以使用Google Cloud Build缓存自定义构建步骤图像? It appears to re-download them every build regardless of latest vs specific tags used in the name, which makes things slower as opposed to faster. 无论名称中使用的latest vs特定标记如何,它似乎都会在每次构建时重新下载它们,这会使事情变得更慢而不是更快。

This is not possible today. 今天这是不可能的。 There are official Cloud Build buildsteps that are cached, but all custom build steps will be pulled. 有缓存的官方Cloud Build构建步骤,但所有自定义构建步骤都将被拉出。 You can minimize the pull latency by using one of the official buildsteps as a base image of your custom build step. 您可以使用其中一个官方构建步骤作为自定义构建步骤的基本映像,最大限度地减少延迟延迟。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 按分支谷歌云平台过滤构建步骤 - Filter build steps by branch google cloud plateform 默认情况下,Google Cloud Build 是否在步骤之间保留 docker 张图像? - Does Google Cloud Build keep docker images between steps by default? Google Cloud Functions - 自定义构建步骤 - Google Cloud Functions - custom build step 将Datalab的自定义版本部署到Google Cloud平台 - Deploying a custom build of Datalab to Google Cloud platform 谷歌云构建 - 自定义机器类型 - Google cloud build - custom machine type 谷歌云构建 - Google Cloud Build 在云构建步骤中安装google-chrome不能跨步骤共享(使用卷) - Installing google-chrome in cloud build step not shared across steps (using volumes) 为什么 Google Cloud Build 在 cloudbuild.yaml 文件中没有任何配置的情况下在步骤之间传递数据 - Why Google Cloud Build is passing data between steps without any configuration in cloudbuild.yaml file 带有 Kaniko 的 Google Cloud Build 没有缓存,所有 dockerbuild 每次都从头开始 - Google Cloud Build with Kaniko is not caching, all dockerbuilds start from scratch each time Cloud Build 步骤中的 Cloud Run 集成测试? - Cloud Run integration tests within Cloud Build steps?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM