Building a DevOps Pipeline with Cloud Run Reviews

68189 reviews

Divya A. · Reviewed almost 5 years ago

Maksym T. · Reviewed almost 5 years ago

Betina S. · Reviewed almost 5 years ago

NA

yogeswararao c. · Reviewed almost 5 years ago

Vishnupriya v. · Reviewed almost 5 years ago

Rohan K. · Reviewed almost 5 years ago

Abhinav V. · Reviewed almost 5 years ago

Prakash R. · Reviewed almost 5 years ago

Patricio T. · Reviewed almost 5 years ago

Minjeong J. · Reviewed almost 5 years ago

Jeffrey C. · Reviewed almost 5 years ago

Pier C. · Reviewed almost 5 years ago

Uziel A. · Reviewed almost 5 years ago

JT S. · Reviewed almost 5 years ago

Kankai Z. · Reviewed almost 5 years ago

Jean Claude M. · Reviewed almost 5 years ago

Dmytrii B. · Reviewed almost 5 years ago

Alan, C. · Reviewed almost 5 years ago

Jibrin H. · Reviewed almost 5 years ago

Praveen K. · Reviewed almost 5 years ago

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. · Reviewed almost 5 years ago

Terry H. · Reviewed almost 5 years ago

Er L. · Reviewed almost 5 years ago

X T. · Reviewed almost 5 years ago

Antonio F. · Reviewed almost 5 years ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.