<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Jenkins Continuous-Delivery on Roger Welin</title><link>https://rogerwelin.github.io/categories/jenkins-continuous-delivery/</link><description>Recent content in Jenkins Continuous-Delivery on Roger Welin</description><generator>Hugo -- 0.155.0</generator><language>en-us</language><lastBuildDate>Tue, 18 Oct 2016 18:43:43 +0000</lastBuildDate><atom:link href="https://rogerwelin.github.io/categories/jenkins-continuous-delivery/feed.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins 2.0 - Next Generation of Pipeline as Code</title><link>https://rogerwelin.github.io/2016/10/18/jenkins-2.0-next-generation-of-pipeline-as-code/</link><pubDate>Tue, 18 Oct 2016 18:43:43 +0000</pubDate><guid>https://rogerwelin.github.io/2016/10/18/jenkins-2.0-next-generation-of-pipeline-as-code/</guid><description>&lt;p&gt;I’ve recently been working with the new pipeline plugin dsl in Jenkins 2.0 and the more I work with it the more I like it - I truly believe that it’s the next generation of pipeline as code even though it has several limitations and gotchas that I will describe.&lt;/p&gt;
&lt;!-- more --&gt;
&lt;h3 id="a-brief-history-of-pipelines-and-job-generation-in-jenkins"&gt;A brief history of pipelines and job generation in Jenkins&lt;/h3&gt;
&lt;p&gt;Pre Jenkins 2.0 was simply not designed for complex Continuous Delivery pipelines. What the community created with plugins such as &lt;a href="https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin"&gt;Build pipeline plugin&lt;/a&gt; and &lt;a href="https://wiki.jenkins-ci.org/display/JENKINS/Delivery+Pipeline+Plugin"&gt;Delivery pipeline plugin&lt;/a&gt; was basically a hack, sewing together separate jobs by passing parameters to them. While functionally it was basically just a big ugly hack underneath with lots of overhead.&lt;/p&gt;</description></item></channel></rss>