Continuous Deployment with Jenkins v1.6 Reviews
6238 reviews
Allan D. · Reviewed מעל 6 שנים ago
Wu W. · Reviewed מעל 6 שנים ago
Nicolas C. · Reviewed מעל 6 שנים ago
There is a small inaccuracy in the Jenkinsfile of the sample-app. It contains a different zone than that was previously set (us-central1-f), so that the pipeline is not built until one corrects it manually.
Alexander C. · Reviewed מעל 6 שנים ago
Jenkins build failed with ERROR: (gcloud.builds.submit) INVALID_ARGUMENT: invalid build: invalid image name "gcr.io/REPLACE_WITH_YOUR_PROJECT_ID/gceme:new-feature.1" contains uppercase letters
Ken L. · Reviewed מעל 6 שנים ago
Jenkins cannot start, always init error
Ken L. · Reviewed מעל 6 שנים ago
Jenkins cannot start, always init error
Ken L. · Reviewed מעל 6 שנים ago
I was not able to finish the lab, since it was not possible to install jenkins via helm. According to log jenkins was not able to download some plugins, with kubernetes plugin among them.
Alexander C. · Reviewed מעל 6 שנים ago
second part did not succeed, branches were visible in Jenkins but all failed.
Hans-Rudolf W. · Reviewed מעל 6 שנים ago
Shane M. · Reviewed מעל 6 שנים ago
Ashish G. · Reviewed מעל 6 שנים ago
임용훈 임. · Reviewed מעל 6 שנים ago
Santanu B. · Reviewed מעל 6 שנים ago
William L. · Reviewed מעל 6 שנים ago
Панов П. · Reviewed מעל 6 שנים ago
Emrah B. · Reviewed מעל 6 שנים ago
Prashant R. · Reviewed מעל 6 שנים ago
Jacob K. · Reviewed מעל 6 שנים ago
Esteban C. · Reviewed מעל 6 שנים ago
Hemanth B. · Reviewed מעל 6 שנים ago
Hemanth B. · Reviewed מעל 6 שנים ago
Arun Lad L. · Reviewed מעל 6 שנים ago
I miss an explanation of the cli commands.
Mikhail P. · Reviewed מעל 6 שנים ago
I have a few problems in this lab. Part "Creating the Jenkins Pipeline": "Step 4: Paste the HTTPS clone URL of your sample-app repo in Cloud Source Repositories into the Project Repository field. Replace [PROJECT_ID] with your GCP Project ID:" and given text "https://source.developers.google.com/p/[PROJECT_ID]/r/default". In screenshot after, line in field "Project repository" inds with "gceme", not "default". Text "The first run of the master job might fail until you make a few code changes in the next step." What's mean "job might fail"? Is pipeline is pretty unstable? In part "Kick off Deployment"' i got failed build again, with fail message: com.google.api.client.googleapis.json.GoogleJsonResponseException: 404 Not Found { "code" : 404, "errors" : [ { "domain" : "global", "message" : "Not found: projects/qwiklabs-gcp-984f7173e9765a4d/zones/us-east1-d/clusters/jenkins-cd.", "reason" : "notFound" } ], "message" : "Not found: projects/qwiklabs-gcp-984f7173e9765a4d/zones/us-east1-d/clusters/jenkins-cd.", "status" : "NOT_FOUND" } at com.google.api.client.googleapis.json.GoogleJsonResponseException.from(GoogleJsonResponseException.java:146) at com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:113) at com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:40) at com.google.api.client.googleapis.services.AbstractGoogleClientRequest$1.interceptResponse(AbstractGoogleClientRequest.java:321) at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1067) at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:419) at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:352) at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:469) at com.google.jenkins.plugins.k8sengine.client.ContainerClient.getCluster(ContainerClient.java:64) at com.google.jenkins.plugins.k8sengine.KubernetesEngineBuilder.perform(KubernetesEngineBuilder.java:249) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE And no clue from lab, what can go wrong. So, build fails and the remaining lab (starting from "curl \ http://localhost:8001/api/v1/namespaces/new- feature/services/gceme-frontend:80/proxy/version") doesn't worked.
Pavel G. · Reviewed מעל 6 שנים ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.