Opinie (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. · Sprawdzono prawie 8 lat temu

christian b. · Sprawdzono prawie 8 lat temu

Great!

Anu P. · Sprawdzono prawie 8 lat temu

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. · Sprawdzono prawie 8 lat temu

not too bad but i hate jenkins :)

Rocky O. · Sprawdzono prawie 8 lat temu

not too bad but i hate jenkins :)

Rocky O. · Sprawdzono prawie 8 lat temu

shravan c. · Sprawdzono prawie 8 lat temu

good

Maria V. · Sprawdzono prawie 8 lat temu

santosh k. · Sprawdzono prawie 8 lat temu

Mohammed E. · Sprawdzono prawie 8 lat temu

Thien H. · Sprawdzono prawie 8 lat temu

Super

Omveer S. · Sprawdzono prawie 8 lat temu

Warren F. · Sprawdzono prawie 8 lat temu

Encountered obstacles with git commit

Raghavendra P. · Sprawdzono prawie 8 lat temu

Ian H. · Sprawdzono prawie 8 lat temu

Francesco V. · Sprawdzono prawie 8 lat temu

Arthi A. · Sprawdzono prawie 8 lat temu

Rohith G. · Sprawdzono prawie 8 lat temu

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. · Sprawdzono prawie 8 lat temu

Richard H. · Sprawdzono prawie 8 lat temu

Will R. · Sprawdzono prawie 8 lat temu

Evandro S. · Sprawdzono prawie 8 lat temu

nice to work here

Abhaya D. · Sprawdzono prawie 8 lat temu

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. · Sprawdzono prawie 8 lat temu

Marshell R. · Sprawdzono prawie 8 lat temu