Jenkins 2.0 Beta
It&#x27;s great to see that Jenkins is following the path blazed by GoCD[1] and Concourse[2] to make the pipeline concept more central.<p>That said, this appears to be achieved by promoting the <i>plugin</i> into the default installation.<p>It also misses some of additional the advantage Concourse holds over Jenkins and GoCD: build configuration is purely declarative and can be checked in with the project. You know what version of your pipeline built the software at any point in its history. And you have a reasonable shot at recreating that build, because every task in every job is run in a fresh container.<p>These are killer features, in my view. Jenkins can be extended with plugins to try to sorta-kinda do either or both, but it&#x27;s not part of the central organising concept of how it works. Windows can run some POSIX apps, but it&#x27;s not a nix.<p>Further out, the Jenkins pipelines are tricky to do fan-out&#x2F;fan-in with; in Concourse it&#x27;s trivial. You have to lay out your pipeline in Jenkins, Concourse will lay it out automatically based on declarative information about each job. Rather than a very rich API for plugins, Concourse boils the unit of extension down to &quot;resources&quot;, which with three actions (check, get, put) can model points in time, git commits, S3 files, version numbers, interacting with a complex product repository and so on.<p>I used to <i>tolerate</i> CI&#x2F;CD, as a necessary and worthy PITA. Now I find myself actively looking for regular tasks, resources, sanity checks and so on I can put into Concourse, so that I don&#x27;t have to remember them or write them up in a wiki.<p>Disclaimer: I work for Pivotal, which sponsors Concourse development. But I wouldn&#x27;t rave about it if I wasn&#x27;t such a convert.<p>[1] <a href="https:&#x2F;&#x2F;www.go.cd&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.go.cd&#x2F;</a><p>[2] <a href="http:&#x2F;&#x2F;concourse.ci&#x2F;" rel="nofollow">http:&#x2F;&#x2F;concourse.ci&#x2F;</a>