How iesgn/tdd-jenkins-kitchen-dond works
Project type and purpose
• This is not a typical web app but a container-based CI/CD toolchain for infrastructure automation.
• It bundles Jenkins, Test Kitchen (with Ansible, Inspec), Cookiecutter templates and Docker-on-Docker to build and test infrastructure code in ephemeral containers.
High-level component analysis
Top-level files:
• Dockerfile + docker-compose.yml → define a single “Jenkins + Kitchen” container, mounting host Docker socket.
• assets/bin/entrypoint.sh & plugins.txt → bootstrap Jenkins (install plugins, configure jobs).
• volumes/jenkins → persistent Jenkins home and job definitions.
• kitchen-docker-*.gem → custom Test Kitchen Docker driver inside the container.
• requirements.txt → Python deps for cookiecutter templating.
Key README insights
• The container image includes Jenkins, Ruby (Test Kitchen & custom gem), Python (cookiecutter), Ansible, Inspec.
• Workflow: developers generate infra-test projects via Cookiecutter → Jenkins jobs invoke kitchen commands → kitchen driver spins up Docker containers → Ansible provisions → Inspec/Serverspec run tests → containers are destroyed.
• The host Docker daemon is shared (mounted socket) to allow kitchen to launch nested containers.