Continuous deployment with Jenkins avis

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. · Examiné il y a presque 8 ans

christian b. · Examiné il y a presque 8 ans

Great!

Anu P. · Examiné il y a presque 8 ans

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. · Examiné il y a presque 8 ans

not too bad but i hate jenkins :)

Rocky O. · Examiné il y a presque 8 ans

not too bad but i hate jenkins :)

Rocky O. · Examiné il y a presque 8 ans

shravan c. · Examiné il y a presque 8 ans

good

Maria V. · Examiné il y a presque 8 ans

santosh k. · Examiné il y a presque 8 ans

Mohammed E. · Examiné il y a presque 8 ans

Thien H. · Examiné il y a presque 8 ans

Super

Omveer S. · Examiné il y a presque 8 ans

Warren F. · Examiné il y a presque 8 ans

Encountered obstacles with git commit

Raghavendra P. · Examiné il y a presque 8 ans

Ian H. · Examiné il y a presque 8 ans

Francesco V. · Examiné il y a presque 8 ans

Arthi A. · Examiné il y a presque 8 ans

Rohith G. · Examiné il y a presque 8 ans

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. · Examiné il y a presque 8 ans

Richard H. · Examiné il y a presque 8 ans

Will R. · Examiné il y a presque 8 ans

Evandro S. · Examiné il y a presque 8 ans

nice to work here

Abhaya D. · Examiné il y a presque 8 ans

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. · Examiné il y a presque 8 ans

Marshell R. · Examiné il y a presque 8 ans