PetClinic / DevOps
CMU 17-636 · Spring PetClinic extension · 2026
A DevOps course extension of Spring PetClinic, with Jenkins builds, Ansible deployment, security checks, and Prometheus/Grafana monitoring.
A course extension of the open-source Spring PetClinic app. The diagrams show the documented VM setup, not a live deployment.
View repositoryTwo environments
Environment boundaries from the repository's VM setup guide.
Configured tools, not a report of current test results.
Different checks
Build, code analysis, and running-app security checks serve different purposes. No current pass result is shown.
After deployment
The documented monitoring setup. This is an architecture drawing, not live telemetry.
Implementation notes
Use an existing application to study delivery.
The application comes from the open-source Spring PetClinic project. The course work adds deployment and operations configuration. The PetClinic application itself is upstream work.
Build in one environment, deploy into another.
The setup guide separates the development container from the host's Vagrant VM. Jenkins builds the application and uses Ansible to deploy it to the VM. SonarQube and OWASP ZAP are part of the documented quality and security workflow.
Keep the deployment inspectable.
Prometheus and Grafana configuration, setup scripts, and screenshots are committed alongside the pipeline. The repository also contains Kubernetes manifests. The documented VM workflow is the basis of this case study; no currently running production deployment is claimed.