DevOps

1. flow-diagram-of-tools-used-in-devops-b8d9f944ef21
2.  5-tools-to-complete-your-CI-pipeline
3.  devops-diagram-generator
4.  why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c
5.  https://blog.gruntwork.io/
6.  cloudformation-vs-terraform-vs-ansible
7.  cicd-tools-throwdown-jenkins-vs-teamcity-vs-bamboo
8.  bamboo-vs-jenkins
9.  CAPS (Chef, Ansible, Puppet, Salt) are mainly for centrally controlling what lives inside a large number of instances. I.e. processes, files, etc. • Terraform and CloudFormation are mainly for creating instances themselves (and other cloud resources like load balancers etc). • I say "mainly" because both bleed a little into the other domain. E.g. CAPS often have capabilities to create instances etc, although not with as much power as terraform / CF. Likewise, one can use Terraform & CF to control the insides of instances at least at startup (via init scripts) and on GCE if you set up a metadata hook you can do it ongoingly as well. I read also other things but more or less the summary is this , use the CAPS tool to do what they were created for (configuration management) and the same for Terraform/Cloudformation create infrastructure. There is only one case where I choose a CAPS tool to build infrastructure and it is when I need a simple infrastructure with virtual machines and I need also to configure these machines. In this case I have the benefit to use 1 tool instead of 2 so I reduce complexity
10.  Which-is-best-Bamboo-or-Jenkins-CI
11.  what-is-the-point-of-a-build-server
12.