Continuously Integrating Puppet
summary
Continuous integration for Puppet combines Jenkins, Vagrant, rspec‑puppet, puppet‑lint and a custom Jenkins job set to run catalog compilation with predetermined facts, static parsing and module tests, plus dynamic deployment to short‑lived test VMs provisioned via Fog/Cobbler/IPA. A tiny Jenkins parser flags puppet agent errors; full rebuild scripts exercise provisioning to catch repo or package drift. Typical run takes ~4 minutes across ~7 critical test nodes and uses canary server builds before merging.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:55Continuous Integration • The practice of frequently integrating one's new or changed code with the existing code
- 3:39Actual Deployment!
- 4:30Vagrant File
- 6:03Pre-commit Hooks
- 6:49Puppet Dynamic Env's
- 7:27Jenkins install
- 10:44Static Analysis
- 12:33Module Testing
- 14:05Catalog Testing
- 17:29Dynamic Analysis
- 18:52Test Deployments
- 21:58Nightly Rebuild
- 28:58Canaries
- 29:57Going Live!
- 31:20Code is available
- 32:04LOPSA-East Panel
- 33:01Contact Info
related talks
40mJenkins and Chef: Infrastructure CI and Application Deployment
01h 12mPitfalls of Continuous Deployment
27mJenkins with Ruby on Rails
28mPractical Puppet: Systems Building Systems
05mIgnite Vox Pupuli
15mPuppet and containers: A multi-tenancy deployment
42mPuppet Control-Repo to the Next Level
28mFrom Monitoring to Automated Testing of Your Infrastructure Code