We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Declarative Pipelines in Jenkins

Formal Metadata

Title
Declarative Pipelines in Jenkins
Subtitle
A new way to define your pipelines in Jenkins
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
Pipeline is quickly establishing itself as the direction that Jenkins jobs aregoing, enabling the definition of a complete CD pipeline in a single job;Pipeline as Code via the “Jenkinsfile”; job durability across master restarts;and more. I’ll be talking here about the next evolution for Pipeline that isjust now hitting 1.0: a simple, declarative model to define your Pipelineswith no need to write scripts. This configuration syntax for Pipeline allowsyou to automatically configure all stages of your pipeline, the complete buildenvironment, post-build actions, notifications and more. All while providingsyntactic and semantic validation before the build actually gets going. We'llalso play with the just-released initial version of the Pipeline Editor, builtto work with Declarative!