Continuous deployment with Jenkins recensioni

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. · Recensione inserita quasi 8 anni fa

christian b. · Recensione inserita quasi 8 anni fa

Great!

Anu P. · Recensione inserita quasi 8 anni fa

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. · Recensione inserita quasi 8 anni fa

not too bad but i hate jenkins :)

Rocky O. · Recensione inserita quasi 8 anni fa

not too bad but i hate jenkins :)

Rocky O. · Recensione inserita quasi 8 anni fa

shravan c. · Recensione inserita quasi 8 anni fa

good

Maria V. · Recensione inserita quasi 8 anni fa

santosh k. · Recensione inserita quasi 8 anni fa

Mohammed E. · Recensione inserita quasi 8 anni fa

Thien H. · Recensione inserita quasi 8 anni fa

Super

Omveer S. · Recensione inserita quasi 8 anni fa

Warren F. · Recensione inserita quasi 8 anni fa

Encountered obstacles with git commit

Raghavendra P. · Recensione inserita quasi 8 anni fa

Ian H. · Recensione inserita quasi 8 anni fa

Francesco V. · Recensione inserita quasi 8 anni fa

Arthi A. · Recensione inserita quasi 8 anni fa

Rohith G. · Recensione inserita quasi 8 anni fa

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. · Recensione inserita quasi 8 anni fa

Richard H. · Recensione inserita quasi 8 anni fa

Will R. · Recensione inserita quasi 8 anni fa

Evandro S. · Recensione inserita quasi 8 anni fa

nice to work here

Abhaya D. · Recensione inserita quasi 8 anni fa

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. · Recensione inserita quasi 8 anni fa

Marshell R. · Recensione inserita quasi 8 anni fa