---
title: "Comment by OneLifeVibe on \"Building an End-to-End Event- Driven CI/CD Pipeline with Jenkins, Terraform, Docker,Ansible, Minikube and Floci\" | Hashnode"
description: "This is a really thorough end-to-end build. The part that stood out to me was using Floci to emulate S3 and SNS locally so the event-driven flow could be tested"
url: "https://hashnode.com/posts/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci/6af03249b15941c3419ef031/comment/6af200ee1515ac0c2c2e1705"
---

[Discussion](https://hashnode.com/posts/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci/6af03249b15941c3419ef031)

Comment [Building an End-to-End Event- Driven CI/CD Pipeline with Jenkins, Terraform, Docker,Ansible, Minikube and Floci](https://hashnode.com/posts/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci/6af03249b15941c3419ef031)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[4d ago](https://hashnode.com/posts/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci/6af03249b15941c3419ef031/comment/6af200ee1515ac0c2c2e1705)

This is a really thorough end-to-end build. The part that stood out to me was using Floci to emulate S3 and SNS locally so the event-driven flow could be tested without touching real cloud resources — that keeps the feedback loop fast and the cost at zero while still exercising the real trigger path. Splitting the infrastructure and application work into separate pipelines also makes sense; a Terraform or Ansible change failing should not block an app deploy, and vice versa. The lessons on container isolation and Docker socket permissions are the kind of detail that usually only shows up after hours of debugging, so documenting the fix alongside the setup is genuinely useful. Did you find the readiness and liveness probes caught real issues during rollout, or were they mostly there as a safety net?

[Solomon Ndimu](https://hashnode.com/@sololemonsthedev)

[4d ago](https://hashnode.com/posts/building-an-end-to-end-event-driven-ci-cd-pipeline-with-jenkins-terraform-docker-ansible-minikube-and-floci/6af03249b15941c3419ef031/comment/6af200ee1515ac0c2c2e1705#reply-6af23495a1bd141a01e3e0a2)

Mostly a safety Net but the startup probe helped a great deal because before the container kept on restarting after failing the liveness probe which was false result because it didn't give the springboot time to startup but after the start-up probe it gave the system time to spin up before the liveness probes is triggered ensuring the probe will actually test an "already started service".