Chef and InSpec Builds with Jenkins
summary
Claim: Jenkins runs Test Kitchen and reports results back to Bitbucket so pull requests fail fast. Implementation uses a multi-branch Jenkins pipeline, Bitbucket stash notifier badges, and either per-repo rake scripts or a centralized Jenkins global library. Outcome: badges appear on PRs, 50+ cookbooks shrink from long Jenkinsfiles to a few lines, faster feedback and fewer broken merges. Tradeoffs: rake files allow local parity; global library scales but feels like a magic voodoo box and limits local testing.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:42Test Kitchen
- 7:32Rake File
- 9:09The Multi-Branch Pipeline in Jenkins
- 9:20Multi-Branch Pipeline
- 13:39Golden Ticket
- 18:32Jenkins Global Libraries
- 18:44Global Libraries
- 27:42Pros and Cons
- 32:41The Push and Pray
related talks
22mMoving Fast Together: Test-Driven Infrastructure
36mIntroduction to Test-kitchen and InSpec
31mContinuous Testing in a DevOps World
23mRSpec: GitHub to Jenkins to Spot Instance Parallelization and Back Again
41mContinuous Integration Tips & Tricks
47mTest Driven Infrastructure with Serverspec & Kitchen CI
43mContinuously Integrating Puppet
01h 21mTest Driving your Rails Infrastructure with Chef