关于“使用 Cloud Run 构建 DevOps 流水线”的评价
68191 条评价
Martin K. · 已于 almost 5 years前审核
TCOD53 P. · 已于 almost 5 years前审核
Divya A. · 已于 almost 5 years前审核
Maksym T. · 已于 almost 5 years前审核
Betina S. · 已于 almost 5 years前审核
NA
yogeswararao c. · 已于 almost 5 years前审核
Vishnupriya v. · 已于 almost 5 years前审核
Rohan K. · 已于 almost 5 years前审核
Abhinav V. · 已于 almost 5 years前审核
Prakash R. · 已于 almost 5 years前审核
Patricio T. · 已于 almost 5 years前审核
Minjeong J. · 已于 almost 5 years前审核
Jeffrey C. · 已于 almost 5 years前审核
Pier C. · 已于 almost 5 years前审核
Uziel A. · 已于 almost 5 years前审核
JT S. · 已于 almost 5 years前审核
Kankai Z. · 已于 almost 5 years前审核
Jean Claude M. · 已于 almost 5 years前审核
Dmytrii B. · 已于 almost 5 years前审核
Alan, C. · 已于 almost 5 years前审核
Jibrin H. · 已于 almost 5 years前审核
Praveen K. · 已于 almost 5 years前审核
TRIGGER CANNOT BE EXECUTED starting build "048c169a-1f92-4574-be9d-997dd9067648" FETCHSOURCE hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch <name> hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m <name> Initialized empty Git repository in /workspace/.git/ From https://source.developers.google.com/p/qwiklabs-gcp-02-179c9a90dca3/r/devops-repo * branch f1f5b4eec4079bac7e3bb6585ad5e55652a3a495 -> FETCH_HEAD HEAD is now at f1f5b4e Testing Build Trigger BUILD Already have image (with digest): gcr.io/cloud-builders/docker unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/student_04_c41f368c4e77/gcp-course/devops-repo/Dockerfile: no such file or directory ERROR ERROR: build step 0 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1
Adalbert M. · 已于 almost 5 years前审核
Terry H. · 已于 almost 5 years前审核
Er L. · 已于 almost 5 years前审核
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。