Jenkins’s key strengths are automation and repeatability of complex continuous delivery processes, but for the vast majority of users, Jenkins’s configuration is a highly manual and too-often error-prone process. Backups alone are critical, resource-consuming tasks. And if a new Jenkins environment has to be configured from scratch, it can bring a team’s productivity to a grinding halt. But what if there was a way to launch a preconfigured Jenkins system customized to your team’s environment with the push of a button?
Mandy Hubbard explains how Care.com uses a customized, script-based startup process and Joyent’s ContainerPilot with a just few edits to a Docker Compose _env file to launch Jenkins in a Docker container. No configuration in the UI is required for Jenkins to start building. Simply run docker-compose up and the environment is ready to go.
With this environment:
Mandy Hubbard is a software engineer and QA architect at Care.com, where she is leading the creation of a CI/CD environment for end-to-end automation of microservices for Care.com’s Financial Services Division. A seasoned professional with over 17 years of QA experience, most of which was spent in fast-paced startup environments driving product quality, Mandy has played a critical role in all stages of software development and has a deep understanding of build-test-deploy processes from development to production.
©2017, O’Reilly UK Ltd • (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