知识卡片
部署顺序与产物存在分别验证
CI的needs说明先后依赖,不会自动共享另一个job本地磁盘或镜像。若发布所需模型来自训练,需显式传递工件并定义依赖;只排好顺序仍可能缺少要发布的真实内容。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 依赖管理实践
原书出处 · 1 处
- · 查看原书依据
needs: [publish-image] # batect.yml containers: deploy-api-container: image: google/cloud-sdk:latest tasks: deploy-api: description: Deploy API image run: container: deploy-api-container command: gcloud run deploy my-model-api --image IMAGE_URL Pseudo-code for: (i) pushing our image from our CI/CD pipeline to a Docker registry and (ii) deploying this image as an API. We would typically need to retag the image to include the specific Docker image registry, but we have left
参考来源
- 位置:《Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)》第04章《依赖管理实践》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)/_epub-src/OEBPS/ch04.html)
- 结论依据:摘录中关于部署顺序与产物存在分别验证的定义、比较或条件支撑卡片;原书表述不严谨的范围已在覆盖记录逐项限定,不把案例结果外推为普遍结论。
- 原始内容:needs: [publish-image] # batect.yml containers: deploy-api-container: image: google/cloud-sdk:latest tasks: deploy-api: description: Deploy API image run: container: deploy-api-container command: gcloud run deploy my-model-api --image IMAGE_URL Pseudo-code for: (i) pushing our image from our CI/CD pipeline to a Docker registry and (ii) deploying this image as an API. We would typically need to retag the image to include the specific Docker image registry, but we have left