Leave a Reply


  1. Reading this from a pure CD standpoint (i.e. ignoring the product bias) , this is a good overview of DTAP pipelines and the beginnings of a CD approach that an engineering team could start to implement (of course choosing those tools that they wish to use and taking on board the advice you give about future state of the players in the CD market).

    The technical implementation however is (while significant) only part of the picture. I am keen to explore how to get actual Development and Operations teams running with this type of scenario, and with their real world applications which tend not to be quite so stateless and in-fact rely on data deployments from time to time too. This however is definitely bookmarked as a good intro to CD which will be useful as a reference, thank you for taking the time to write it up.

    Rob Vanstone Reply

    • Thank you for your comment. I fully agree with you that tools are just one item of continuous delivery. People and processes are just as important. You need motivated people/teams that understand the value of continuous delivery and are able to continuously improve themselves. Further you need the right processes, if it takes days/weeks to get the approvals necessary to go to production, than those processes need to change to support continuous delivery. It’s a lot more than just picking some tools. I can also recommend the Continuous Delivery book by Jez Humble and David Farley, if you want to read more about the subject.

      Johan Janssen Reply

  2. I am not much familier with Jenkins, but by reading this i am getting question, is docker runs on same host where jenkin runs or can be othe host ?

    Dhaval Reply

    • Where Docker is running depends on what you want. You could run Jenkins in a Docker container and than your own application in another Docker container. But you can also run Jenkins directly on the host without using Docker.

      Johan Janssen Reply