Jenkins is an open source automation server with an unparalleled plugin ecosystem to support practically every tool as part of your delivery pipelines. Whether your goal is continuous integration, continuous delivery or something else entirely, Jenkins can help automate it.
Jenkins 2.0 brings Pipeline as code, a new setup experience and other UI improvements all while maintaining total backwards compatibility with existing Jenkins installations.
As organizations of all types seek to deliver high quality software faster, their use of Jenkins is extending beyond just continuous integration (CI) to continuous delivery (CD). In order to implement continuous delivery, teams need a flexible way to model, orchestrate and visualize their entire delivery pipeline.
Jenkins 2.0 supports delivery pipelines as a first-class entity. The Pipeline plugin introduces a domain-specific language (DSL) that helps Jenkins users to model their software delivery pipelines as code, which can be checked in and version-controlled along with the rest of their project's source code.
The expressive domain-specific language makes it easier and faster to create a simple "build, test and deploy" pipeline or build advanced pipelines. The end result is improved productivity for teams.
Jenkinsfile.
The abundant plugin ecosystem means that new Jenkins users must navigate through long lists of plugins to find the most suitable plugins to match their needs. Without any "batteries included" to address the most common needs, getting started with Jenkins can be an intimidating experience.
For new users, Jenkins 2.0 starts up with suggested plugins to get them started with the right set of tools to use Jenkins effectively from day one.
There are a number of user interface improvements, such as the improved job configuration page, to make configuring jobs easier.
Jenkins 2.0 is a drop-in replacement of the Jenkins 1.x series of releases and fully backward compatible. There is practically no reason not to upgrade once 2.0 is released.
We're not done yet! There will be more changes towards Jenkins 2.0, and we'll keep updating this page to highlight them.
We have more details of the 2.0 plan on our wiki!
We're very interested in your feedback on what you think of the Jenkins 2.0 preview releases.
To experience Jenkins 2.0 properly, we recommend you set up a different Jenkins home directory . This way, you'll both get to try the new setup, and keep your production instance safe from possible issues.