HP Presents: Journey to Continuous Delivery Inside HP Using GitHub Enterprise, Chef, and ChatOps - ChefConf 2015
Download as PPTX, PDF0 likes491 views
The document outlines HP's journey towards continuous delivery, emphasizing the roles of champions, incremental changes, and collaboration tools like GitHub and Jenkins. It describes the positive outcomes achieved through automation, such as improved visibility, team collaboration, and consistent deployments. Additionally, it highlights the formation of a dedicated team to assist HP customers in their own continuous delivery transformations.
HP Presents: Journey to Continuous Delivery Inside HP Using GitHub Enterprise, Chef, and ChatOps - ChefConf 2015
- 2. HP Presents: Journey to Continuous Delivery Andy Claiborne & Jared Smartt, April 1st, 2015
- 3. Andy Claiborne @AndyClaiborne veloandy Jared Smartt @JSmartt1 Infrastructure Automation COE, HP
- 4. You’re waiting for a train. A train that will take you far away. You know where you hope this train will take you, but you don’t know for sure. But it doesn’t matter, because we’ll be together. This is the story of our journey to Continuous Delivery
- 5. HP is huge
- 6. Let’s zoom in to…
- 7. Just our lab
- 8. About 220 engineers working on about a dozen projects
- 9. A year ago
- 10. What we did about it GitHub Enterprise Continuous Delivery
- 11. How We Built It Out
- 12. Strategy • Find champions within organization • Small de-risking experiments • Roll out change incrementally • Continually demonstrate value • Listen to teams • Pick appropriate battles
- 13. GitHub Pull Request Builder Plug-in 1. Let’s Collaborate!
- 14. 2. Jenkins: Not just for PRs anymore Sinatra App Centralized logic of what to call when we receive an event GitHub API
- 15. 2. Jenkins: Not just for PRs anymore Chef Server Sinatra App Centralized logic of what to call when we receive an event GitHub API System sudo chef-client
- 16. 3. Deployments API Chef Server
- 17. What’s Awesome: Automation stays out of developers’ way Projects can pick-and-choose what to adopt
- 18. What a Chef recipe pull request looks like to a developer
- 19. What a Deployment looks like to a developer
- 20. Started with low-risk, low-visibility projects Demonstrated value: • Iterate faster with better visibility • Better team collaboration with less time wasted • Able to fix problems faster • Systems and deployments are consistent Now using these methods to develop HP Support Automation 2.0 – Large, high-visibility project Pattern used for a bunch of different projects
- 21. Add system provisioning to pipeline Move more teams on board Improving existing automation Still more to do internally in my lab
- 22. Our lab now
- 23. Exciting times in my lab, but zooming out…
- 24. Challenges in the neighborhood: Isolated GitHub Enterprise instance
- 25. Exciting times at HP: Continuous Delivery Pilot New policies emphasize enabling dev teams using whatever delivery pipeline works for them. Focus on API for shared reporting/compliance.
- 26. The situation before my lab’s transformation isn’t atypical of large customers. A lot of large companies are facing the same need to migrate to a culture of continuous delivery New HP Datacenter Infrastructure Automation COE team formed to help HP Datacenter Care customers through their own Continuous Delivery journeys Jared and Andy are just some of the team members “on the ground” helping HP customers deliver value faster all day, every day. Exciting time to be an HP customer