Continuous deployment with Jenkins Reviews

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. · Reviewed almost 8 years ago

christian b. · Reviewed almost 8 years ago

Great!

Anu P. · Reviewed almost 8 years ago

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. · Reviewed almost 8 years ago

not too bad but i hate jenkins :)

Rocky O. · Reviewed almost 8 years ago

not too bad but i hate jenkins :)

Rocky O. · Reviewed almost 8 years ago

shravan c. · Reviewed almost 8 years ago

good

Maria V. · Reviewed almost 8 years ago

santosh k. · Reviewed almost 8 years ago

Mohammed E. · Reviewed almost 8 years ago

Thien H. · Reviewed almost 8 years ago

Super

Omveer S. · Reviewed almost 8 years ago

Warren F. · Reviewed almost 8 years ago

Encountered obstacles with git commit

Raghavendra P. · Reviewed almost 8 years ago

Ian H. · Reviewed almost 8 years ago

Francesco V. · Reviewed almost 8 years ago

Arthi A. · Reviewed almost 8 years ago

Rohith G. · Reviewed almost 8 years ago

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. · Reviewed almost 8 years ago

Richard H. · Reviewed almost 8 years ago

Will R. · Reviewed almost 8 years ago

Evandro S. · Reviewed almost 8 years ago

nice to work here

Abhaya D. · Reviewed almost 8 years ago

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. · Reviewed almost 8 years ago

Marshell R. · Reviewed almost 8 years ago