Building a DevOps Pipeline Reviews

Sujit T. · Reviewed about 2 years 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 about 2 years ago

Roberto R. · Reviewed about 2 years ago

Sudheesh R. · Reviewed about 2 years 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 about 2 years ago

Sujit T. · Reviewed about 2 years ago

Aleksander B. · Reviewed about 2 years ago

Aditya Y. · Reviewed about 2 years ago

Mohamed Ali B. · Reviewed about 2 years ago

sunil k. · Reviewed about 2 years ago

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

SAUMEN D. · Reviewed about 2 years ago

Hermanio S. · Reviewed about 2 years ago

Suzani P. · Reviewed about 2 years 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 about 2 years ago

Igor K. · Reviewed about 2 years 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 about 2 years ago

Hoang T. · Reviewed about 2 years ago

Daniel S. · Reviewed about 2 years 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 about 2 years 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 about 2 years 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 about 2 years ago

Task 5 is missing info about service account

Maciej G. · Reviewed about 2 years ago

Rahul D. · Reviewed about 2 years ago

Sudhahar S. · Reviewed about 2 years ago

service account required, cloud run didn't work

GREG P. · Reviewed about 2 years ago