20533C Continuous Delivery and Continuous Deployment

20533C Continuous Delivery and Continuous Deployment

For customers with complex websites and workloads it is important to have a clean and automated approach to deployment

Its not just a case of getting it "out there" but also to be able to incorporate changes into the sites without much disruption or loss of transactions from connected customers or users.

https://technologyconversations.com/2016/01/14/the-short-history-of-cicd-tools/
https://fabric8.io/guide/cdelivery.html
https://elasticbox.com/documentation/integrate-with-jenkins/setting-up-ci-cd/

Chef and PuppetLabs have become popular platforms for automation, especially when dealing with linux-based workloads

Jenkins is another tool we have discussed as we look at building a CI/CD pipeline
http://www.slideshare.net/martinmalek92/ci-and-cd-with-jenkins
http://developers.redhat.com/blog/2016/09/13/using-jenkins-in-the-red-hat-cicd-ecosystem/
http://www.methodsandtools.com/archive/archive.php?id=121

Of late, the name "octopus" has surfaced
This article shows how to combine Octopus with Teamcity
https://blog.jetbrains.com/teamcity/2015/11/automating-deployments-with-teamcity-and-octopus-deploy/

The concept of packaging is also related

NUGET packaging

https://docs.nuget.org/ndocs/create-packages/creating-a-package