Serverless Data Processing with Dataflow - CI/CD with Dataflow recensioni

João P. · Recensione inserita circa 3 anni fa

Jatin L. · Recensione inserita circa 3 anni fa

Great

Thirumalai S. · Recensione inserita circa 3 anni fa

Gonzalo A. · Recensione inserita circa 3 anni fa

Felipe C. · Recensione inserita circa 3 anni fa

Cesar G. · Recensione inserita circa 3 anni fa

I got several errors despite following given steps student_00_4d80561dcf8a@cloudshell:~/ci-cd-for-data-processing-workflow/env-setup (qwiklabs-gcp-01-e56d723f2352)$ gcloud composer environments create $COMPOSER_ENV_NAME \ --location $COMPOSER_REGION \ --zone $COMPOSER_ZONE_ID \ --python-version 2 ERROR: (gcloud.composer.environments.create) INVALID_ARGUMENT: Found 1 problem: 1) Invalid python version: [2]. Python version may be either '3' or left empty. and later on starting build "6fb27bf1-d88e-4a8b-b708-eed0578518ef" FETCHSOURCE hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch <name> hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m <name> Initialized empty Git repository in /workspace/.git/ From https://source.developers.google.com/p/qwiklabs-gcp-01-e56d723f2352/r/data-pipeline-source * branch 994f43df1be9bf9e697b19c56502a5eb783e063c -> FETCH_HEAD HEAD is now at 994f43d change in test files BUILD Starting Step #0 - "check-out-source-code" Step #0 - "check-out-source-code": Already have image (with digest): gcr.io/cloud-builders/git Step #0 - "check-out-source-code": Cloning into 'data-pipeline-source'... Finished Step #0 - "check-out-source-code" Starting Step #1 - "build-jar" Step #1 - "build-jar": Already have image (with digest): gcr.io/cloud-builders/mvn:3.5.0-jdk-8 Finished Step #1 - "build-jar" Starting Step #2 - "deploy-jar" Step #2 - "deploy-jar": Already have image (with digest): gcr.io/cloud-builders/gsutil Step #2 - "deploy-jar": BucketNotFoundException: 404 gs://project-composer-dataflow-source bucket does not exist. Finished Step #2 - "deploy-jar" ERROR ERROR: build step 2 "gcr.io/cloud-builders/gsutil" failed: step exited with non-zero status: 1

Omaira O. · Recensione inserita circa 3 anni fa

Georgios C. · Recensione inserita circa 3 anni fa

Arya K. · Recensione inserita circa 3 anni fa

Khushal P. · Recensione inserita circa 3 anni fa

Ramakoti K. · Recensione inserita circa 3 anni fa

Thanks

Alan Ignacio S. · Recensione inserita circa 3 anni fa

Khushal P. · Recensione inserita circa 3 anni fa

Fazil M. · Recensione inserita circa 3 anni fa

Nonitha V. · Recensione inserita circa 3 anni fa

To pass the lab successfully user needs to use the following commit: https://github.com/GoogleCloudPlatform/ci-cd-for-data-processing-workflow/commit/f900b51106a2189f7bc2dacffc9760952b0bd245

Andrei U. · Recensione inserita circa 3 anni fa

There is a problem to deploy DAG to Composer.

Andrei U. · Recensione inserita circa 3 anni fa

Cannot complete this lab because this error occurs In Task: Task 1: Create the build and test pipeline, the execution does not go beyond Step #9, logging the error message: Finished Step #9 - "wait-for-dag-deployed-on-composer" ERROR ERROR: build step 9 "gcr.io/cloud-builders/gcloud" failed: step exited with non-zero status: 1

Vinícius R. · Recensione inserita circa 3 anni fa

Cannot complete this lab because this error occurs In Task: Task 1: Create the build and test pipeline, the execution does not go beyond Step #9, logging the error message: Finished Step #9 - "wait-for-dag-deployed-on-composer" ERROR ERROR: build step 9 "gcr.io/cloud-builders/gcloud" failed: step exited with non-zero status: 1

Vinícius R. · Recensione inserita circa 3 anni fa

Build fails unexpectedly. Not enough resources to get help on the issues.

Jatin L. · Recensione inserita circa 3 anni fa

The build pipeline is breaking at step 9. In airflow servers, we can see this erros on DAGS tab: Broken DAG: [/home/airflow/gcs/dags/data-pipeline-test.py] No module named providers.google.cloud.transfers.gcs_to_local . I don't know if it's missing the whole module, or maybe something changed but i don't know how to fix it

Renata E. · Recensione inserita circa 3 anni fa

Task 2 in Creating Cloud Build pipelines repeatedly fails, even though the previous step is marked as completed.

Anna B. · Recensione inserita circa 3 anni fa

Matheus S. · Recensione inserita circa 3 anni fa