Jenkins Pipeline Provides Easier Ways to Create and Maintain Software Delivery Pipelines

Jenkins community announces new functionality for Jenkins Pipeline, making it easier to create and maintain software delivery pipelines

Jenkins vs Hudson - CloudBeesFOSDEM – Brussels, Belgium – 2 February 2017 - The Jenkins project , comprised of a community of practitioners using Jenkins, announced a new, simpler way to automate continuous delivery pipelines. Jenkins Pipeline announces both declarative syntax and an initial version of a graphical Pipeline editor, making it significantly easier for DevOps teams - and especially non-programmers - to create and maintain continuous delivery (CD) pipelines. CloudBees, Inc. , the hub of enterprise Jenkins and DevOps, collaborated with the Jenkins community to develop the Pipeline Model Definition plugin that provides this new functionality.

With the introduction of the new functionality, Jenkins Pipeline now offers users multiple ways for DevOps teams to create and maintain CD pipelines using a method that matches their pipeline sophistication requirements, programming skill and CD experience level. The new release provides a declarative syntax, an initial version of a graphical editor and shared pipeline libraries.

The new release of Jenkins Pipeline:

  • Improves usability by making pipeline functionality available to novices and experts, programmers and non-programmers alike

  • Increases DevOps team productivity by enabling users to rapidly create CD pipelines across a wide range of complexity – from simple to multi-branch complexity

  • Accelerates adoption of CD through ease of use, reuse and extensibility

CD pipelines can be inherently complex, making it difficult for team members of varying skills – from developers to IT operations to management – to programmatically create pipelines. The functionality provided in Jenkins Pipeline now enables any user to easily build and maintain CD pipelines either graphically or with code. For example, Declarative Pipeline Syntax allows construction of pipelines using simple, predefined format to define the stages and steps in a pipeline. This provides a straightforward structure and simplified flow, making software pipeline creation accessible to all users.

"Declarative pipeline combines the power of the flexibility of Jenkins Pipeline and the simplicity of Blue Ocean, the new user experience for Jenkins,” said Kohsuke Kawaguchi, Jenkins founder and CTO at CloudBees. "Defining and evolving continuous delivery pipeline is made not only easier but also pleasant, which is an important milestone for making continuous delivery accessible for everyone.”

Jenkins is the most popular open source automation server in use today, with over 133,000 active installations and 1,000,000+ users. Jenkins 2, a significant release issued by the community in 2016, has been rapidly adopted, with almost 50 percent of active Jenkins installations using it* at year-end. Jenkins offers the most extensive plugin ecosystem for automating and orchestrating continuous delivery pipelines.

Additional Resources

*2016 Jenkins Community Survey, conducted by CloudBees for the Jenkins community:

About Jenkins and the Jenkins Community
Jenkins is the leading open source automation server supported by a large and growing community of developers, testers, designers and other people interested in continuous integration, continuous delivery and other modern software delivery practices. Built on the Java Virtual Machine (JVM), it provides more than 1,200 plugins that extend Jenkins to automate with practically any technology software delivery teams use.

The Jenkins community advocates the use of Jenkins to the global development community, serving as a central source for tutorials, forums and other helpful resources for Jenkins users of all experience-levels. By recognizing the numerous contributors to the Jenkins project, the Jenkins project creates and fosters a community-powered infrastructure for maintaining and further developing Jenkins. You can follow the Jenkins community on Twitter (@JenkinsCI ).

Media Contact:
Katelyn Campbell
PAN Communications