Opiniones sobre Cómo trabajar con Cloud Build

Scott K. · Se revisó hace 26 días

Lisha J. · Se revisó hace 26 días

THANMAYEE A. · Se revisó hace 26 días

Lab doesn't give any feeling like other labs gave me. It feels like overly/unknown ones. Seems I need to study bit more about containers, images, docker, dockerfile.

Vinoth Kumar R. · Se revisó hace 26 días

ADITYA R. · Se revisó hace 26 días

VASANTHARAJ S. · Se revisó hace 26 días

MOHAMED ISMAIL P S. · Se revisó hace 26 días

MEJE B. · Se revisó hace 26 días

Khairunnisa M. · Se revisó hace 26 días

Azhar K. · Se revisó hace 26 días

Sharath H. · Se revisó hace 26 días

Anh T. · Se revisó hace 26 días

ARCHANA N S. · Se revisó hace 26 días

NICSEN A S. · Se revisó hace 26 días

Kishan M. · Se revisó hace 26 días

Preetam G. · Se revisó hace 26 días

A small errata: a text around command "gcloud builds submit --config cloudbuild2.yaml" says "run build for cloudbuild.yaml" where "2" is missing.

Maksim A. · Se revisó hace 26 días

Mariale C. · Se revisó hace 26 días

Lisha J. · Se revisó hace 26 días

SAI DARSHAN S. · Se revisó hace 26 días

AKARSH R. · Se revisó hace 26 días

Ето един добре структуриран текст на английски език, който можеш да използваш за обратна връзка (feedback) към Qwiklabs или за твоя отчет. Текстът описва опита ти балансирано – какво е било полезно и къде са били препъникамъните. Lab Feedback & Evaluation What I Liked (Pros) The lab provides a very practical, hands-on approach to understanding the core CI/CD capabilities of Google Cloud. Building a custom pipeline using Artifact Registry and Cloud Build is essential for any DevOps workflow. I particularly appreciated Task 4, which demonstrated how Cloud Build handles step failures, as it simulates real-world troubleshooting scenarios. Challenges Encountered (Cons) I encountered significant difficulties with the gcloud CLI syntax for creating build triggers. The INVALID_ARGUMENT error appeared multiple times despite following the logical parameters. The issue: There seems to be a strict requirement for specific flags (like --tag vs --config) that isn't always clear in the automated validation scripts. The fix: I had to re-run commands from the root directory and ensure the exact naming conventions expected by the "Check my progress" button were met, rather than using more advanced/automated scripts. Overall Rating: 4/5 Content: ⭐⭐⭐⭐⭐ (Very relevant and well-structured) Guidance: ⭐⭐⭐ (CLI documentation within the lab could be more specific regarding region/global constraints to avoid validation errors) Difficulty: Moderate Summary (Short version for a comment box): "Great lab for learning Cloud Build and Artifact Registry. However, I faced some INVALID_ARGUMENT errors when using the CLI for triggers. It would be helpful if the lab instructions specified exactly which flags the 'Check my progress' script is looking for. Once I aligned the syntax with the validation requirements, everything worked perfectly. Very insightful Task 4 on failure handling!" Best Regards

Betta Z. · Se revisó hace 26 días

Done

Gargi B. · Se revisó hace 26 días

Preeti P. · Se revisó hace 26 días

Phil L. · Se revisó hace 26 días