3 ms·
I'm quite disappointed by the "Continuous Delivery" section. I expected tools that let you model a Continuous Delivery pipeline, like http://concourse.ci/ http
by perlgeek 10y ago
I'm quite disappointed by the "Continuous Delivery" section.
I expected tools that let you model a Continuous Delivery pipeline, like http://concourse.ci/ http://concourse.ci/, https://go.cd/ https://go.cd/, or Jenkins with the Pipelines plugin (directly included in Jenkins 2.0+, iirc).
Tools like Maven and Ant would be only a step in such a pipeline.
I guess this reinforces the OPs point that the whole devops nomenclature is very fractured, and folks use terms from this field as they please.
- deleted 10y ago[deleted]
- jarrettcoggin 10y agoI completely agree. That section was a gross misunderstanding of what Continuous Delivery actually is. It should have actually been called "Packaging". The "Continuous Delivery" section was more about versioned packaging (and vendoring dependencies into packages), while the automation section was about configuration management of servers (which included deploying versioned packages). If someone wants to understand what Continuous Delivery actually is (which is pretty well understood), there's a great book on the topic called... oddly enough... "Continuous Delivery" by Jez Humble. It covers CD pipelines like you mentioned, while also covering a bunch of the other listed topics at a high level in a much better way. Granted it's an actual book, but it's worth it's place on an DevOps/Release/Software Engineer's desk when implemented appropriately.
- jk563 10y agoIt's an excellent book that I highly recommend. A lot to get through but it never gets difficult to read, and they (David Farley co-authored) include many anecdotes of when things have gone both right and wrong to demonstrate the points they make.