Jenkins 2.0
Jenkins 2.0 has a different design methodology and flow compared to Jenkins 1.0. Instead of using freestyle jobs, there is a new Domain Specific Language (DSL) that is an abbreviated form of the Groovy programming language.
The Pipeline views also function differently to how they do in Jenkins 1.0. The Pipeline stage views also help us visualize the various stages in a pipeline.
Why move to Jenkins 2.0?
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...