Jenkins 2.0 Beta

Jenkins 2.0 is currently in


. We encourage you to download it, try it out, and give us your


but for production systems please continue to use the current



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
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.

Beta Downloads

Download the .war
Download native packages

Highlights of 2.0:


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


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.

Key Features and Benefits of Pipelines

Pipeline as Code

  • Easily define simple and complex pipelines through the DSL in a Jenkinsfile.
  • Pipeline as code provides a common language to help teams (e.g. Dev and Ops) work together.
  • Easily share pipelines between teams by storing common “steps” in shared repositories.

Pipeline Stage View

  • A new interface makes it easy to visualize the progress across an entire pipeline.


  • Pipelines are long-lasting and can survive infrastructure outages.

Built-in support for Git, GitHub branches

  • Each feature branch can define its own delivery pipeline, which Jenkins can detect, automatically managing Pipelines when branches are created or deleted.


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.

Key Features and Benefits of Improved Usability

New “Getting Started” experience

  • Start with a set of suggested plugins that match the most common needs.

Redesigned “Create Item” page

  • The “Create Item” page has been redesigned to include icons for job types.
    Once you have a larger number of item types to choose from, the page will group item types by category.

New Job Configuration page

  • Tabs at the top of the job configuration page let you quickly jump to various sections on the form.
    The redesigned form elements make it easy to tell which options are related.

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.

Give us feedback!

We’re very interested in your feedback on what you think of the Jenkins 2.0 beta release.

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.

Original URL:  

Original article

Comments are closed.

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: