Continuous deployment with Jenkins Ulasan

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. · Diulas hampir 8 tahun lalu

christian b. · Diulas hampir 8 tahun lalu

Great!

Anu P. · Diulas hampir 8 tahun lalu

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. · Diulas hampir 8 tahun lalu

not too bad but i hate jenkins :)

Rocky O. · Diulas hampir 8 tahun lalu

not too bad but i hate jenkins :)

Rocky O. · Diulas hampir 8 tahun lalu

shravan c. · Diulas hampir 8 tahun lalu

good

Maria V. · Diulas hampir 8 tahun lalu

santosh k. · Diulas hampir 8 tahun lalu

Mohammed E. · Diulas hampir 8 tahun lalu

Thien H. · Diulas hampir 8 tahun lalu

Super

Omveer S. · Diulas hampir 8 tahun lalu

Warren F. · Diulas hampir 8 tahun lalu

Encountered obstacles with git commit

Raghavendra P. · Diulas hampir 8 tahun lalu

Ian H. · Diulas hampir 8 tahun lalu

Francesco V. · Diulas hampir 8 tahun lalu

Arthi A. · Diulas hampir 8 tahun lalu

Rohith G. · Diulas hampir 8 tahun lalu

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. · Diulas hampir 8 tahun lalu

Richard H. · Diulas hampir 8 tahun lalu

Will R. · Diulas hampir 8 tahun lalu

Evandro S. · Diulas hampir 8 tahun lalu

nice to work here

Abhaya D. · Diulas hampir 8 tahun lalu

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. · Diulas hampir 8 tahun lalu

Marshell R. · Diulas hampir 8 tahun lalu