建立開發運作管道 Reviews

Shaik Mohammed I. · Reviewed over 2 years ago

Konrad B. · Reviewed over 2 years ago

JeanPaul S. · Reviewed over 2 years ago

Michael M. · Reviewed over 2 years ago

Sateesh S. · Reviewed over 2 years ago

Nino K. · Reviewed over 2 years ago

Shawn C. · Reviewed over 2 years ago

Thomas D. · Reviewed over 2 years ago

Raksha P. · Reviewed over 2 years ago

David P. · Reviewed over 2 years ago

Dukil P. · Reviewed over 2 years ago

Harun K. · Reviewed over 2 years ago

easy piecy

Vince C. · Reviewed over 2 years ago

Sato K. · Reviewed over 2 years ago

Thomas D. · Reviewed over 2 years ago

Ivan V. · Reviewed over 2 years ago

Mahesh U. · Reviewed over 2 years ago

Warissara N. · Reviewed over 2 years ago

Viet P. · Reviewed over 2 years ago

Hamid-Reza K. · Reviewed over 2 years ago

Ignacio S. · Reviewed over 2 years ago

Jose F. · Reviewed over 2 years ago

really cool exercise. I learned how to build an image from a Dockerfile and store it in the Artifact Registry. I learned that if the source code changes, the image must change as well. An image is source code + environment requirements (e.g. packages needed for source code to run) plus any set up scripts (set up tasks prior to code run). I also learned how to automate the updating of image upon a change in the source code using Cloud Build Triggers. My one question is, once the image changes, we need to re-deploy it on a GCE instance. That is, we must create a new VM and deploy the container. This is a manual process in the lab. How would one automate this? If this cannot be automated then it is of little benefit that the image build can be automated.

Diana R. · Reviewed over 2 years ago

Robert Frederick P. · Reviewed over 2 years ago

David M. · Reviewed over 2 years ago