I like CI tools that run locally on a developer machine and run end to end tests with all Microservices locally. The secret is integrating early and often. Tha

I like CI tools that run locally on a developer machine and run end to end tests with all Microservices locally. The secret is integrating early and often. That's why I wrote mazzle and platform-up. Mazzle is a run server that is configured as a Graphviz file (.dot) and defines an end to end environment. Here's an example graph file of a pipeline: https://github.com/samsquire/mazzle/blob/master/docs/architecture.tb.png https://github.com/samsquire/mazzle/blob/master/docs/archite... It's largely a prototype of an idea. It's infrastructure and pipelines as code but incorporates every tool you use from terraform, chef, ansible, puppet, Kubernetes, packer and shell scripts. My example code spins up a Consul and Kubernetes cluster with hashicorp vault and a Debian repository server, configured SSH keys on every worker, bastion and Java application. And Prometheus exporter and grafana. I haven't got around to adding ELK yet. But it didn't take long to do all these things due to Mazzle meaning it's very easy to test complicated changes together. https://devops-pipeline.com https://devops-pipeline.com - Mazzle Platform up is a pattern for local development that tests your Microservices locally all together. You use vagrant-lxc and ansible together to deploy everything locally. So you can test your secret management locally and deployment process. If your ELK stack is ansible driven you can even run your ELK stack locally as I did on a client project. https://GitHub.com/samsquire/platform-up https://GitHub.com/samsquire/platform-up