DevOps パイプラインの構築 のレビュー

Tah Sujit · 約2年前にレビュー済み

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.

Abdelmoulah David · 約2年前にレビュー済み

Rampone Roberto · 約2年前にレビュー済み

Radhakrishnan Sudheesh · 約2年前にレビュー済み

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

WOO Thierry · 約2年前にレビュー済み

Tah Sujit · 約2年前にレビュー済み

Borowicz Aleksander · 約2年前にレビュー済み

Yadav Aditya · 約2年前にレビュー済み

Ben Souissi Mohamed Ali · 約2年前にレビュー済み

kumar sunil · 約2年前にレビュー済み

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

DAS SAUMEN · 約2年前にレビュー済み

Santana Hermanio · 約2年前にレビュー済み

Prado Dos Reis Suzani · 約2年前にレビュー済み

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.

Hartmann Keith · 約2年前にレビュー済み

Kazuki Igor · 約2年前にレビュー済み

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

Egyed Gábor · 約2年前にレビュー済み

Trung Hieu Hoang · 約2年前にレビュー済み

Songi Daniel · 約2年前にレビュー済み

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.

Vallesi Claudio · 約2年前にレビュー済み

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.

Dahan Jeff · 約2年前にレビュー済み

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

Lerner Dan · 約2年前にレビュー済み

Task 5 is missing info about service account

Grzywacz Maciej · 約2年前にレビュー済み

Deshwal Rahul · 約2年前にレビュー済み

Subramaniam Sudhahar · 約2年前にレビュー済み

service account required, cloud run didn't work

PARKINS GREG · 約2年前にレビュー済み