This content is part of the Essential Guide: Effective DevOps tooling for accelerated continuous delivery adoption

Declarative Jenkins pipeline the latest new feature in DevOps tooling

Listen to this podcast

Looking to get more out of your DevOps tooling? The declarative Jenkins pipeline helps take continuous integration and continuous delivery to new heights.

The Jenkins 2.0 release was more evolutionary than it was revolutionary, but one feature was anticipated more than all the other DevOps tooling enhancements combined, and that was the formal integration of the Jenkins pipeline. Well, Jenkins has managed to take continuous integration and continuous deployment tooling to the next level by improving on the late 2016 release with the enhanced, declarative Jenkins pipeline.

Now the pipeline hasn't actually changed since the 2.0 release. What has changed with the introduction of the declarative Jenkins pipeline is how developers can use and interact with this powerful DevOps tool. "It's one of the most flexible and powerful pipeline implementations out there," says Sacha Labourey, CEO of CloudBees when talking about the pipeline DevOps tooling. But to new users, the Jenkins pipeline can seem a bit intimidating, and the syntax can scare novice users away, stifling adoption of this very powerful DevOps tooling. The declarative Jenkins pipeline aims to address this.

Simplified DevOps tooling

Sacha LaboureySacha Labourey

"The problem is that when you start with pipeline, you are not a sophisticated user. The learning curve is too high for new users," said Labourey of the original version of the pipeline DevOps tooling. But the new, declarative Jenkins pipeline is "an extremely easy way to create pipelines using a very simple language," said Labourey. "There is also a graphic editor where you can point and click and create pipelines very easily."

And the good news is that under the covers, whether the declarative approach or the traditional approach is employed, it's all the same DevOps tooling implementing continuous integration and simplifying continuous delivery. So you can gain comfort using the declarative approach, move to a more traditional syntax when looking to take advantage of more advanced Jenkins pipeline features, and all of the code will be compatible.

To learn more about the DevOps tooling, the declarative Jenkins pipeline and the results of the 2016 CloudBees User survey, listen to the accompanying podcast of the interview with TheServerSide's Cameron McKenzie and CloudBees CEO Sacha Labourey.

Next Steps

Have you tried Jenkins? Bamboo? Your DevOps tooling choices abound

Give these Jenkins plug-ins a try

What is the future of Jenkins PaaS?

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

What changes to the declarative Jenkins pipeline, or any DevOps tooling for that matter, would make your job of doing continuous integration and continuous delivery easier?