Continuous Deployment with Jenkins v1.6 Reviews

A handy template for starting with Jenkins

Oleg B. · Reviewed almost 7 years ago

Saket K. · Reviewed almost 7 years ago

Alejandro M. · Reviewed almost 7 years ago

Very good!

James L. · Reviewed almost 7 years ago

Hemank L. · Reviewed almost 7 years ago

Maciej M. · Reviewed almost 7 years ago

In section "Deploying to production", the text reads "Create a canary branch and push it to the Git server:" but I think it should say something like Merge canary branch to master and push master to the Git server:" Also, for the git user.email and user.name, it is not entirely clear what to enter for "Replace [EMAIL_ADDRESS] with your Git email address and [USERNAME] with your Git username:" It should be your lab account email address and your lab account username?

Tracy S. · Reviewed almost 7 years ago

Bart?omiej W. · Reviewed almost 7 years ago

Brijesh S. · Reviewed almost 7 years ago

Ben W. · Reviewed almost 7 years ago

Jose M. · Reviewed almost 7 years ago

Charles I. · Reviewed almost 7 years ago

yessine h. · Reviewed almost 7 years ago

Matthew A. · Reviewed almost 7 years ago

Jayesh M. · Reviewed almost 7 years ago

Riccardo M. · Reviewed almost 7 years ago

Henry C. · Reviewed almost 7 years ago

Carl R. · Reviewed about 7 years ago

bugs in implementation instructions. Jenkins was missing plugins.

Morgan H. · Reviewed about 7 years ago

Donghua L. · Reviewed about 7 years ago

Jenkins configuration involves manually installing Kubernetes (like thrugh Jenkins web UI), while the lab mentions the plugin, it does not list that it needs additional user action to install it.

Anna W. · Reviewed about 7 years ago

The lab is broken.

Igor D. · Reviewed about 7 years ago

Hard to get Jenkins picking up new branch from git to start new build

Maya W. · Reviewed about 7 years ago

Quan S. · Reviewed about 7 years ago

Mike M. · Reviewed about 7 years ago