Continuous deployment with Jenkins avaliações

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. · Revisado há almost 8 years

christian b. · Revisado há almost 8 years

Great!

Anu P. · Revisado há almost 8 years

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. · Revisado há almost 8 years

not too bad but i hate jenkins :)

Rocky O. · Revisado há almost 8 years

not too bad but i hate jenkins :)

Rocky O. · Revisado há almost 8 years

shravan c. · Revisado há almost 8 years

good

Maria V. · Revisado há almost 8 years

santosh k. · Revisado há almost 8 years

Mohammed E. · Revisado há almost 8 years

Thien H. · Revisado há almost 8 years

Super

Omveer S. · Revisado há almost 8 years

Warren F. · Revisado há almost 8 years

Encountered obstacles with git commit

Raghavendra P. · Revisado há almost 8 years

Ian H. · Revisado há almost 8 years

Francesco V. · Revisado há almost 8 years

Arthi A. · Revisado há almost 8 years

Rohith G. · Revisado há almost 8 years

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. · Revisado há almost 8 years

Richard H. · Revisado há almost 8 years

Will R. · Revisado há almost 8 years

Evandro S. · Revisado há almost 8 years

nice to work here

Abhaya D. · Revisado há almost 8 years

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. · Revisado há almost 8 years

Marshell R. · Revisado há almost 8 years