Building a DevOps Pipeline Reviews

Sujit T. · Reviewed בערך 2 שנים ago

The Cloud Build Trigger can not be created without a service account. I tried adding a service account with the Cloud Build Service Account role. Then I get an error message when running the trigger indicating : Failed to trigger build: generic::invalid_argument: if 'build.service_account' is specified, the build must either (a) specify 'build.logs_bucket', (b) use the REGIONAL_USER_OWNED_BUCKET build.options.default_logs_bucket_behavior option, or (c) use either CLOUD_LOGGING_ONLY / NONE logging options I guess you need to specify these options with a cloud build yaml file, which we don't have in this lab since it is solely based on a Dockerfile. Long story short, you need to correct this lab for it to work with the current rules with Cloud Build. In the same vein, Cloud Source Repositories seems to be on its way to deprecation.

David A. · Reviewed בערך 2 שנים ago

Roberto R. · Reviewed בערך 2 שנים ago

Sudheesh R. · Reviewed בערך 2 שנים ago

Cloud Build ne fonctionne pas du tout Erreur suivante : Failed to trigger build: generic::invalid_argument: if 'build.service_account' is specified, the build must either (a) specify 'build.logs_bucket', (b) use the REGIONAL_USER_OWNED_BUCKET build.options.default_logs_bucket_behavior option, or (c) use either CLOUD_LOGGING_ONLY / NONE logging options

Thierry W. · Reviewed בערך 2 שנים ago

Sujit T. · Reviewed בערך 2 שנים ago

Aleksander B. · Reviewed בערך 2 שנים ago

Aditya Y. · Reviewed בערך 2 שנים ago

Mohamed Ali B. · Reviewed בערך 2 שנים ago

sunil k. · Reviewed בערך 2 שנים ago

the lab is something wrong while creating trigger. Giving service account access issue.

SAUMEN D. · Reviewed בערך 2 שנים ago

Hermanio S. · Reviewed בערך 2 שנים ago

Suzani P. · Reviewed בערך 2 שנים ago

Lab instructions are missing important steps. The VM would not work with debian 12, had to use debian 11. The Build Trigger requires a service account, but none of the existing service accounts worked.

Keith H. · Reviewed בערך 2 שנים ago

Igor K. · Reviewed בערך 2 שנים ago

Though I was able to verify my progress, the trigger did not work, it failed every time with the following error msg: Your build failed to run: generic::invalid_argument: if 'build.service_account' is specified, the build must either (a) specify 'build.logs_bucket', (b) use the REGIONAL_USER_OWNED_BUCKET build.options.default_logs_bucket_behavior option, or (c) use either CLOUD_LOGGING_ONLY / NONE logging options I have tried to select all available service accounts for the triggger. The instruction has not tell anything about the service accounts, but without selecting one the trigger could not be saved

Gábor E. · Reviewed בערך 2 שנים ago

Hoang T. · Reviewed בערך 2 שנים ago

Daniel S. · Reviewed בערך 2 שנים ago

Instructions are wrong or outdated. The trigger configuration require a service account but nothing was explained. There are two service account available but despite that, an error was still shown. The lab allow you to continue and check as "done" the next steps anyway. Absolutely worthless lab.

Claudio V. · Reviewed בערך 2 שנים ago

got an error about when I specify a service account for the trigger that it requires a build bucket. I did not see where to add this.

Jeff D. · Reviewed בערך 2 שנים ago

This lab started to break down. Commands are apparently out of date and would not work. The interface has apparently changed and no longer reflects what should be done. I ended up just clicking through the check status option and that got me to 100%. This definitely NEEDS to be updated

Dan L. · Reviewed בערך 2 שנים ago

Task 5 is missing info about service account

Maciej G. · Reviewed בערך 2 שנים ago

Rahul D. · Reviewed בערך 2 שנים ago

Sudhahar S. · Reviewed בערך 2 שנים ago

service account required, cloud run didn't work

GREG P. · Reviewed בערך 2 שנים ago