How rabiaadel/cicd-petclinic works
Project type and purpose
• This is a full-stack Java web application (Spring PetClinic) extended with a dual CI/CD automation layer (Jenkins and GitHub Actions), containerization (Docker, Docker Compose), infrastructure provisioning (Terraform), Kubernetes deployment (K8s manifests), and monitoring (Prometheus, Grafana).
• Purpose: deliver the PetClinic application reliably and repeatedly through automated build, test, code-quality analysis, container registry publishing, and deployment to cloud infrastructure.
File structure
• Top-level source:
• src/main/java + resources → Spring Boot MVC application (controllers, repositories, entities, templates, static assets, configuration).
• src/test/java + jmeter → unit, integration, and performance tests.
• CI/CD definitions:
• Jenkinsfile (self-hosted Jenkins declarative pipeline).
• .github/workflows/*.yml → GitHub Actions workflows.
• Containerization & local deployment:
• Dockerfile + docker-compose.yml.
• Infra provisioning:
• infra/*.tf → Terraform scripts (VPC, EC2, security groups).
• Kubernetes deployment:
• k8s/db.yml + k8s/petclinic.yml.
• Monitoring & observability:
• prometheus.yml + grafana/provisioning/datasource.yml.
README insights
• CI/CD stages: checkout, build/compile, test, SonarQube quality gate, Docker build, push to Nexus, deploy via Docker Compose or SSH.
• GitHub Actions: build, test, SonarQube scan.
• Technologies: Maven, JDK17, SonarQube, Nexus, Docker, Jenkins, GitHub Actions.
Elements
• Source & version control (blue)
• CI/CD tools (orange)
• Infra provisioning (green)
• Container registry (purple)
• Runtime / cluster (teal)
• Monitoring (yellow)