August 2018
Intermediate to advanced
416 pages
12h 37m
English
So, to begin with, why move to Jenkins 2.0 at all and not stay with Jenkins 1.0? The Jenkins Classic views are considered to be cluttered and did not take ease of use into account. Jenkins 2.0 made a big push on using Docker Images in a more intuitive manner. Also, the new UI includes a Jenkins pipeline editor and changes the way you find your builds by introducing a pipeline view. The goal for the new UI is to reduce clutter and increase clarity for every member of a team that uses Jenkins. The new UI also has GitHub and Bitbucket integration as well as Git integration. The Jenkins 2.0 UI is essentially a collection of plugins that you install called Blue Ocean.
Read now
Unlock full access