Membangun Pipeline DevOps Ulasan

Sujit T. · Diulas sekitar 2 tahun lalu

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. · Diulas sekitar 2 tahun lalu

Roberto R. · Diulas sekitar 2 tahun lalu

Sudheesh R. · Diulas sekitar 2 tahun lalu

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. · Diulas sekitar 2 tahun lalu

Sujit T. · Diulas sekitar 2 tahun lalu

Aleksander B. · Diulas sekitar 2 tahun lalu

Aditya Y. · Diulas sekitar 2 tahun lalu

Mohamed Ali B. · Diulas sekitar 2 tahun lalu

sunil k. · Diulas sekitar 2 tahun lalu

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

SAUMEN D. · Diulas sekitar 2 tahun lalu

Hermanio S. · Diulas sekitar 2 tahun lalu

Suzani P. · Diulas sekitar 2 tahun lalu

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. · Diulas sekitar 2 tahun lalu

Igor K. · Diulas sekitar 2 tahun lalu

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. · Diulas sekitar 2 tahun lalu

Hoang T. · Diulas sekitar 2 tahun lalu

Daniel S. · Diulas sekitar 2 tahun lalu

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. · Diulas sekitar 2 tahun lalu

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. · Diulas sekitar 2 tahun lalu

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. · Diulas sekitar 2 tahun lalu

Task 5 is missing info about service account

Maciej G. · Diulas sekitar 2 tahun lalu

Rahul D. · Diulas sekitar 2 tahun lalu

Sudhahar S. · Diulas sekitar 2 tahun lalu

service account required, cloud run didn't work

GREG P. · Diulas sekitar 2 tahun lalu