How long does it take to deploy a configuration change to production? Ten minutes? An hour? A day? Weeks? For many years, developers have been moving toward continuous delivery models for their primarily web-based applications. There are numerous benefits gained by increasing discipline and automation and regularly deploying software, but many of these practices have not seen rapid adoption by operations and infrastructure teams.
R. Tyler Croy offers an overview of continuous delivery concepts and puts them into practice by building a continuous delivery pipeline with Jenkins to test, stage, and deploy infrastructure code to production. Tyler explains how reducing the effort, error rate, and time it takes to deploy a configuration to change to production means less time fighting fires and more time doing what you want.
All materials and demos will be accompanied by actual real-life infrastructure code.
R. Tyler Croy is a longtime Jenkins contributor, having tended the Jenkins project’s own infrastructure for almost as long as it has existed. Originally guiding the project from artisanal, hand-crafted physical machines into the world of Puppet and reproducible infrastructure. Tyler has most recently been focused on improving the reliability, testability, and immutability of the Jenkins project infrastructure with Puppet, ServerSpec, and Docker.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org