关于“使用 Cloud Build 的 Google Kubernetes Engine 流水线”的评价

30566 条评价

Kushal G. · 已于 20 days前审核

Rajat L. · 已于 20 days前审核

Swapnil s. · 已于 20 days前审核

Mahika G. · 已于 20 days前审核

Completed the lab successfully.

Sachin C. · 已于 20 days前审核

Aditi S. · 已于 20 days前审核

Paras S. · 已于 20 days前审核

Harsh P. · 已于 20 days前审核

Tanishq W. · 已于 20 days前审核

First sign up to github then do anything else Open the hello-cloudbuild-deploy trigger one last time. Ensure the Name is exactly hello-cloudbuild-deploy (all lowercase, no spaces). Ensure the Region is exactly us-east4. Ensure the Source is the candidate branch.

Bhavish C. · 已于 20 days前审核

Jit G. · 已于 20 days前审核

Nidhi T. · 已于 20 days前审核

Nitish K. · 已于 20 days前审核

Varsha S. · 已于 20 days前审核

Suggestion: The checkpoints > Create the Continuous Integration (CI) Pipeline and > Create the Test Environment and CD Pipeline seem to only work with GitHub. It may be worth adding options to work with GitLab Enterprise connectors, as company policy restricts the use of personal GitHub accounts. A couple of errata: Task 6 Under the heading "Grant Cloud Build access to GKE", > Replace [your-github-username] with your personal GitHub username: should instead say > Replace ${GITHUB-USERNAME} with your GitHub username. as under the section "Configure the build". Task 9 > Click the View all link under Build History for the hello-cloudbuild-env repository. This should say "hello-cloudbuild-deploy" because the dashboard shows the name of the triggers. > Click Rebuild. The button now says "Retry build". The screenshot also needs an update.

Gerardus Samudra S. · 已于 20 days前审核

Madhavi K. · 已于 20 days前审核

Harshita C. · 已于 20 days前审核

Aryan K. · 已于 20 days前审核

Md R. · 已于 20 days前审核

Tharun T. · 已于 20 days前审核

thanks

Dnyaneshwar G. · 已于 20 days前审核

prabhat p. · 已于 20 days前审核

Swapnil C. · 已于 20 days前审核

Bhargavi P. · 已于 20 days前审核

Bhushan P. · 已于 20 days前审核

我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。