Continuous deployment with Jenkins Rezensionen

There's a leap from the last lab to this one, and the gap is bigger than the gaps between the previous labs, so it was a little jarring.

Nate N. · Vor fast 8 Jahre überprüft

christian b. · Vor fast 8 Jahre überprüft

Great!

Anu P. · Vor fast 8 Jahre überprüft

The stuff with Git was kind of annoying because I had to use my private account for work coursework. Also, some of the text replacement wasn't as noticeable to me (as it has been in other sessions) and I messed some stuff up.

Zach W. · Vor fast 8 Jahre überprüft

not too bad but i hate jenkins :)

Rocky O. · Vor fast 8 Jahre überprüft

not too bad but i hate jenkins :)

Rocky O. · Vor fast 8 Jahre überprüft

shravan c. · Vor fast 8 Jahre überprüft

good

Maria V. · Vor fast 8 Jahre überprüft

santosh k. · Vor fast 8 Jahre überprüft

Mohammed E. · Vor fast 8 Jahre überprüft

Thien H. · Vor fast 8 Jahre überprüft

Super

Omveer S. · Vor fast 8 Jahre überprüft

Warren F. · Vor fast 8 Jahre überprüft

Encountered obstacles with git commit

Raghavendra P. · Vor fast 8 Jahre überprüft

Ian H. · Vor fast 8 Jahre überprüft

Francesco V. · Vor fast 8 Jahre überprüft

Arthi A. · Vor fast 8 Jahre überprüft

Rohith G. · Vor fast 8 Jahre überprüft

CONS: 1) The initial pod got a configError state instead of successful that was a result of the initial ssl stuff. 2) The ingress didn't feel like working because of 1) as it resulted to an UNHEALTHY state. This was not covered by the lab, nor were the cases where the newly created certificates did not work. I had to google tons of stuff to get the info on what was going wrong and then google a bunch of stuff on how to delete the secret, pods, services, ingresses etc. (+ points for having them all in a namespace) 3) new_feature branch had a hardcoded put your own id value in a file somewhere that is not mentioned in the tutorial and I had to go through jenkins build failure logs to get what's wrong, after having to deal with the ssl shenanigans of 1)-2) PROS: 1) Enough time to search for answers is something goes wrong. 2) Pretty educational. Can't go above 3 stars as this lab is pretty unstable compared to the previous ones

Ioannis K. · Vor fast 8 Jahre überprüft

Richard H. · Vor fast 8 Jahre überprüft

Will R. · Vor fast 8 Jahre überprüft

Evandro S. · Vor fast 8 Jahre überprüft

nice to work here

Abhaya D. · Vor fast 8 Jahre überprüft

Create a Repository to host the sample app source code Step 1 Create a copy of the gceme sample app and push it to Cloud Source Repositories. Needs to be more clear

JI Y. · Vor fast 8 Jahre überprüft

Marshell R. · Vor fast 8 Jahre überprüft