Continuous deployment with Jenkins Reviews

Mauricio D. · Reviewed около 8 лет ago

Igor R. · Reviewed около 8 лет ago

very little explanation on the commands

Thiago A. · Reviewed около 8 лет ago

Juan C. · Reviewed около 8 лет ago

Caique D. · Reviewed около 8 лет ago

Adrian D. · Reviewed около 8 лет ago

Thiago R. · Reviewed около 8 лет ago

Michal S. · Reviewed около 8 лет ago

Javier V. · Reviewed около 8 лет ago

exclente lab

Christopher P. · Reviewed около 8 лет ago

In the midle of this lab I lose my internet connection and I have some problems to restart the activity, I think that may be important instructions for troubleshooting in these cases.

Walter D. · Reviewed около 8 лет ago

Riccardo V. · Reviewed около 8 лет ago

于勇 于. · Reviewed около 8 лет ago

suggest the following modifications to simplify or add clarity step 1 watch -c "kubectl describe ingress jenkins --namespace jenkins | grep backends" step 5 kubectl get pods -n production -l app=gceme -l role=backend -Lapp,role,env --create repo section -- step2 export PROJECT_ID=`gcloud config get-value project` git remote add origin https://source.developers.google.com/p/${PROJECT_ID}/r/default git remote -v

Conor R. · Reviewed около 8 лет ago

Jorge S. · Reviewed около 8 лет ago

Yair B. · Reviewed около 8 лет ago

LTI S. · Reviewed около 8 лет ago

Bruno R. · Reviewed около 8 лет ago

Some actions were taking too much time to change.

Henrique T. · Reviewed около 8 лет ago

Good

Franco Q. · Reviewed около 8 лет ago

There was a problem with the branches and Jenkins. It fails all the builds and It doesn't change the versions from develiopment, canary and the final master.

LTI S. · Reviewed около 8 лет ago

The steps of the modifications in html.go and main.go are not so explicit. It can be skipped because it does not follow the pattern of others. An image or a command would help.

Pedro F. · Reviewed около 8 лет ago

Jesus R. · Reviewed около 8 лет ago

Felipe F. · Reviewed около 8 лет ago

Will B. · Reviewed около 8 лет ago