menu

Continuous Delivery with Jenkins in Kubernetes Engine

Go to Lab

52 Revisar

28db0cefee1bae6870cebf3c5b4db8d8

venkateswarlu c. · Avaliado aproximadamente 16 horas atrás

55a91fe6d4f7d3512b8b78d7d0cfc950

zinedine k. · Avaliado 1 dia atrás

Afcb375edc85ecc87fe7cd7ab7bec75c

Dakota H. · Avaliado 3 dias atrás

E41f7494a2d4fe2378d6ce8dd7ca1ea7

Flacky

Mat M. · Avaliado 3 dias atrás

E24b66fa87ba78e244f470f90f9f77d9

This lab did not work for me. I'll retry it later. "gcloud compute networks create jenkins --mode auto" caused this warning "WARNING: mode is deprecated. Please use subnet-mode instead." After I deployed Jenkins, the pod never reached the "Running" status ; it was in "Pending" status forever "export FRONTEND_SERVICE_IP=$(kubectl get -o \ jsonpath="{.status.loadBalancer.ingress[0].ip}" --namespace=production services gceme-frontend)" resulted in this error "error: output format " jsonpath={.status.loadBalancer.ingress[0].ip}" not recognized"

Ridha H. · Avaliado 5 dias atrás

E7cc7d26a089a25eff5de68f3c81ef5a

Martin S. · Avaliado 5 dias atrás

44f378712e6d586d0d4d992e4937d6d2

Daniel S. · Avaliado 6 dias atrás

A6988df6d7ab83529ee7870844da2554

Hugo A. · Avaliado 7 dias atrás

E7cc7d26a089a25eff5de68f3c81ef5a

Martin S. · Avaliado 9 dias atrás

1837ff2d3807f9004a74282c50e82ca0

Hugues M. · Avaliado 12 dias atrás

1837ff2d3807f9004a74282c50e82ca0

Jenkins pod could not be scheduled: the cpu limit could not be satisfied. Good experience debugging that.

Hugues M. · Avaliado 12 dias atrás

01fca86421da12ba87ced583628c6997

Ashish B. · Avaliado 12 dias atrás

Eadc33e10385853e23416a690bb54a82

ok

Nicolas M. · Avaliado 16 dias atrás

83ddc3c929d4a58d108390c5de41b8cd

My second attempt at this lab....the generation of the jenkins resources is taking too long...have run out of time....also fixing some problems with the scripts...

Sean R. · Avaliado 16 dias atrás

1a4e894b904555b9567a784038dd8428

Cyrille H. · Avaliado 16 dias atrás

Dc476d2ac0281e6e13ac7695ce6cbfe7

Andras K. · Avaliado 17 dias atrás

5a7ce9a6421ecb032d2635a65a01adac

Andrzej L. · Avaliado 17 dias atrás

90e2612187b9426441b7899ec43d695b

Stanley C. · Avaliado 18 dias atrás

83ddc3c929d4a58d108390c5de41b8cd

Some errors in the scripting....the ---zone =auto should be now subnet-zone, the creation of the ingress for jenkins didn't work...the backends remained in state "UNHEALTHY"...I will re-try this lab...blocking the quest at present

Sean R. · Avaliado 19 dias atrás

92608d189e4ecc7083878d3a4ade7a76

Yeongju K. · Avaliado 26 dias atrás

96abe36d4ed6b44d720d0b463590f03a

Byungkee H. · Avaliado 27 dias atrás

060e53deca31656cca67d71d4442db9a

Piotr K. · Avaliado 27 dias atrás

19b5e626ebd1a9ddeb068fa7a7530fee

Ignas G. · Avaliado aproximadamente 1 mês atrás

97da993479dbe9e3e7333df43610832d

The Jenkins cluster was unhealthy till the end of the lab.

Georges M. · Avaliado aproximadamente 1 mês atrás

9828ecf171d5e9f1aee72b1a3c1a5fe8

Natarrajan V. · Avaliado aproximadamente 1 mês atrás