CI Techniques for Delivering the Chef-Repo: Three Case Studies
summary
Chef-based CI automates macOS image creation using kitchen-ci with vagrant tied into VSTS and ships updates weekly; mac VMs are ~8 GB and can take up to 5 minutes to boot so full integration tests are expensive. The project builds domain-driven custom resources (for example a spotlight resource and a defaults resource) that fix real bugs and make intent declarative, and it pairs fast chef-spec and RSpec unit tests with Inspec verification so the pipeline actually works and shortens feedback.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:37The Essential Mac Os Cookbook
- 1:44Why Shuffle for Mac Os at Microsoft
- 3:45Disabling Spotlight
- 5:56Elegant Language
- 8:03Domain Driven Api
- 15:19Out-of-Box Management for Mac Os
- 15:44Compliance with Inspec
- 33:05Splunk and Chef
- 36:45Working with a Cookbook
related talks
41mChef Cookbook Testing Like a Pro
40mJenkins and Chef: Infrastructure CI and Application Deployment
34m"Acing" Infrastructure Testing with Chef
01h 21mTest Driving your Rails Infrastructure with Chef
36mIntroduction to Test-kitchen and InSpec
38mAn Approach to Air-Gapped Deployment
59mCI Best Practices for iOS & macOS App Development
06mTen Quick Tips to Improve Your Chef Workflow