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