Continuous Deployment with Jenkins v1.6 Reviews
6238 reviews
Tetiana K. · Reviewed over 6 years ago
Deepak K. · Reviewed over 6 years ago
Elwin B. · Reviewed over 6 years ago
Will probably run this one several times. Unable to access the side labs (if you're unfamiliar Jenkins - run the jenkins/k8s lab). Would help and enrich the class if they were made available to enterprise users with limited access.
David E. · Reviewed over 6 years ago
David E. · Reviewed over 6 years ago
Samuel F. · Reviewed over 6 years ago
It was a very interesting lab. However, I had two problems: 1) The CLUSTER_ZONE variable on Jenkinsfile was not the same defined on Clone Repository's step 2) I was not able to apply Ctrl+X on Google Shell
Roberto N. · Reviewed over 6 years ago
Jenkins build failed when building sample app
Balasangar B. · Reviewed over 6 years ago
more details about the commands and arguments would be very helpfull
Romain P. · Reviewed over 6 years ago
Suraj H. · Reviewed over 6 years ago
Kahoru H. · Reviewed over 6 years ago
Lab all and all was great. However at the start the lab instructs you to change region/zone to us-central1-f. However in the Jenkinsfile the zone is written as us-east... This causes the deployment to fail because the project cannot be found in that region. I'm not sure if this is intentional however for people that have not used Jenkins before this may be difficult to troubleshoot.
Andrew P. · Reviewed over 6 years ago
SRINIVASA REDDY K. · Reviewed over 6 years ago
Andrew P. · Reviewed over 6 years ago
Dharani M. · Reviewed over 6 years ago
현준 조. · Reviewed over 6 years ago
Baris B. · Reviewed over 6 years ago
Stanley H. · Reviewed over 6 years ago
Clone Repository - the zone defined in the course is conflict with the source codes of jenkins which hard-coded with different zone... Need to fix the config and made the deployment successful.
Dennis C. · Reviewed over 6 years ago
Foon L. · Reviewed over 6 years ago
david y. · Reviewed over 6 years ago
Thomas C. · Reviewed over 6 years ago
Issue has been found by various attendees where the following information will display during the deployment process: [Pipeline] // podTemplate [Pipeline] End of Pipeline com.google.api.client.googleapis.json.GoogleJsonResponseException: 404 Not Found { "code" : 404, "errors" : [ { "domain" : "global", "message" : "Not found: projects/qwiklabs-gcp-09c13ef6bbcda318/locations/asia-east2/clusters/jenkins-cd.", "reason" : "notFound" } ], "message" : "Not found: projects/qwiklabs-gcp-09c13ef6bbcda318/locations/asia-east2/clusters/jenkins-cd.", "status" : "NOT_FOUND" } Other than the issue above, the lab is pretty straight forward and easy to understand.
David Y. · Reviewed over 6 years ago
Billy Y. · Reviewed over 6 years ago
Tony L. · Reviewed over 6 years ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.