Opiniones sobre Continuous deployment with Jenkins

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. · Se revisó hace casi 8 años

christian b. · Se revisó hace casi 8 años

Great!

Anu P. · Se revisó hace casi 8 años

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. · Se revisó hace casi 8 años

not too bad but i hate jenkins :)

Rocky O. · Se revisó hace casi 8 años

not too bad but i hate jenkins :)

Rocky O. · Se revisó hace casi 8 años

shravan c. · Se revisó hace casi 8 años

good

Maria V. · Se revisó hace casi 8 años

santosh k. · Se revisó hace casi 8 años

Mohammed E. · Se revisó hace casi 8 años

Thien H. · Se revisó hace casi 8 años

Super

Omveer S. · Se revisó hace casi 8 años

Warren F. · Se revisó hace casi 8 años

Encountered obstacles with git commit

Raghavendra P. · Se revisó hace casi 8 años

Ian H. · Se revisó hace casi 8 años

Francesco V. · Se revisó hace casi 8 años

Arthi A. · Se revisó hace casi 8 años

Rohith G. · Se revisó hace casi 8 años

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. · Se revisó hace casi 8 años

Richard H. · Se revisó hace casi 8 años

Will R. · Se revisó hace casi 8 años

Evandro S. · Se revisó hace casi 8 años

nice to work here

Abhaya D. · Se revisó hace casi 8 años

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. · Se revisó hace casi 8 años

Marshell R. · Se revisó hace casi 8 años