Distributed Scrum Development with Jenkins, Vagrant, Fabric and Selenium
summary
Uses Jenkins to run full-stack integration and acceptance pipelines for DealerTrack 2.0 across 6+ distributed scrum teams, with a Jenkins master-slave layout and dedicated slaves that cut heavy integrated-build time by about 30%. Builds use Vagrant to spin production-like mini‑stacks, Fabric Python scripts for SSH deploys, Nexus for internal artifacts, and Robotframework‑Selenium on a Selenium grid for UI tests. Enforces >90% coverage, wraps DB schema as a ~700MB package for fast restores, and catches integration breaks before production.
AI-written summary · about
chapters (13)
- 0:00Project context and goals
- 1:43Importance of mindset
- 3:50Scrum integration challenges
- 5:08Single package best practices
- 7:28Automated build and deploy
- 8:47Python fabric for deployment
- 10:57Internal artifact management
- 12:25Automated integration builds
- 14:32Vagrant for testing stack
- 17:18Version and dependency management
- 20:24Scaling Jenkins infrastructure
- 22:27Selenium grid testing
- 24:17Q&A and closing remarks
related talks
30mImplementing Continuous Deployment with Jenkins & Gerritt
44mFrom Zero to Federated at the Speed of Jenkins
01h 12mPitfalls of Continuous Deployment
35mJenkins Scaling and Organization for an Efficient CI
42mJenkins: Enabling Agility and Efficiency- 42mJenkins: Enabling Agility and Efficiency
42mZero to Jenkins: Automatic builds + deploys
51mSetting up a scalable CI platform with jenkins, docker and rancher