Opinie (Building a DevOps Pipeline)

Sujit T. · Sprawdzono około 2 lata temu

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. · Sprawdzono około 2 lata temu

Roberto R. · Sprawdzono około 2 lata temu

Sudheesh R. · Sprawdzono około 2 lata temu

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. · Sprawdzono około 2 lata temu

Sujit T. · Sprawdzono około 2 lata temu

Aleksander B. · Sprawdzono około 2 lata temu

Aditya Y. · Sprawdzono około 2 lata temu

Mohamed Ali B. · Sprawdzono około 2 lata temu

sunil k. · Sprawdzono około 2 lata temu

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

SAUMEN D. · Sprawdzono około 2 lata temu

Hermanio S. · Sprawdzono około 2 lata temu

Suzani P. · Sprawdzono około 2 lata temu

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. · Sprawdzono około 2 lata temu

Igor K. · Sprawdzono około 2 lata temu

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. · Sprawdzono około 2 lata temu

Hoang T. · Sprawdzono około 2 lata temu

Daniel S. · Sprawdzono około 2 lata temu

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. · Sprawdzono około 2 lata temu

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. · Sprawdzono około 2 lata temu

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. · Sprawdzono około 2 lata temu

Task 5 is missing info about service account

Maciej G. · Sprawdzono około 2 lata temu

Rahul D. · Sprawdzono około 2 lata temu

Sudhahar S. · Sprawdzono około 2 lata temu

service account required, cloud run didn't work

GREG P. · Sprawdzono około 2 lata temu