Since it went into service a decade ago,  Jenkins has issued around 700 releases – but this month marks the first time in the Continuous Delivery (CD) platform’s history that it has dropped anything major. Today, Jenkins is ending this modest streak with the release of version 2.0, tuned to meet the demands of a world that has become accustomed to relentless updates.

According to the official blog by CloudBees – the organisation that began life as a PaaS provider and pivoted to become the Jenkins specialist du jour – Pipelines have been the driving idea behind this release, offering, “A means to helping organisations deliver better software faster.”

Commenting on the big drop, Jenkins creator and CloudBees CTO Kohsuke Kawaguchi explained; “As Jenkins user adoption continues to grow into the millions of users, the community has responded with core updates to assure continued, long term success….The Jenkins 2.0 release helps new and existing users implement continuous delivery with the most flexible way to model, orchestrate and visualize the entire delivery pipeline.”

Screen Shot 2016-04-26 at 17.35.59

The Jenkins Pipeline plugins were created  to provide  orchestration for every stage of the software delivery process. With version 2.0, there have been several augmentations, including new ‘Pipeline-as-Code’ functionality, enabling teams to speedily create and collaborate on advanced CD pipelines with code alone. ‘Pipeline Durability’ has also been thrown into the mix to add an extra level of protection against outages by allowing users to resume their workflow at the point of disruption, saving a good deal of frustration. In addition, there’s the new ‘Multibranch’ faculty, offering automatic, zero-configuration of CD pipelines for new branches and pull-requests.

In an interview with the Register, Kawaguchi noted that whilst initially the aim for Jenkins was to allow people to automate their builds and test executions, “now everyone does that.” Instead, the team are focusing more on downstream automation, and “the testing that involves bigger scale or multiple pieces.”

Along with the focus on ensuring the software is fully fit and ready to keep pace with the frenetic rhythm of CD in 2016, there have been updates to a number of core Jenkins capabilities, including a move to give users clearer visibility of delivery stages and enhancements, as well as renovations to get users up and working that bit quicker. Users can tap into new automated install capabilities, and have the option of automatically adding in community-recommended sets of plugins for their projects.

image004

If you’d like to see what Jenkins 2.0 feels like, allow us to discretely usher you to the official download page – and if you’re terribly curious to learn more (and not too busy running around with a lightsaber), there will be a virtual Jenkins Area Meetup on May 4th, 2016.

 

Ten Years in the Pipeline: Jenkins 2.0 is Here

About The Author
- Editor of Voxxed.com, focusing on all things Java, JVM, cloud-y, methodical, future-fantastic, and everything in between. Got a piece of news, article or tutorial you'd like to share with your fellow Voxxians? Drop us a line at info@voxxed.com

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>