Puppet
51 Case Studies
A Puppet Case Study
GitHub needed to scale and standardize its server configuration while making infrastructure work accessible to software developers, not just ops. With a years-old Puppet codebase and many developers unfamiliar with Puppet, the company faced the challenge of reducing ops bottlenecks and enabling self-service provisioning without disrupting existing workflows.
Their solution was to treat Puppet like any other development project: maintain a Puppet repo, write manifests and tests, and build tooling—puppet-lint, rspec-puppet and librarian-puppet—to provide style checks, automated testing and dependency management. Paired with documentation and training, this made Puppet workflows familiar to developers (test, branch, deploy), increased developer contributions to infrastructure, and reduced reliance on ops while improving reliability—practices they now share at PuppetConf.
Jesse Newland
Systems Engineer