Creating a Pipeline - LeanAgileKC 2015
•
0 j'aime•472 vues
Slides from LeanAgileKC 2015 talk
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Creating a Pipeline - LeanAgileKC 2015
Similaire à Creating a Pipeline - LeanAgileKC 2015 (20)
Plus de Aaron Blythe
Dernier
Dernier (20)
Creating a Pipeline - LeanAgileKC 2015
- 1. Aaron Blythe Continuous Delivery Pipeline Aaron Blythe 1
- 2. @ablythe Aaron Blythe Sr. Automation and System Engineer - Hearst Business Media http://aaronblythe.org/ Answering Questions Writing Code http://www.meetup.com/DevOps-Kansas-City/ Running Meetups 2
- 3. @ablythe 3
- 4. @ablythe 4
- 5. @ablythe 5
- 6. @ablythe 6
- 7. @ablythe 7
- 8. @ablythe 8
- 9. @ablythe 9
- 11. @ablythe "Treat your delivery pipeline as the heartbeat of your organization." @DibbeEdwards #DOES15 11
- 12. @ablythe What is a Pipeline? 12
- 13. @ablythe 13
- 14. @ablythe 14
- 15. @ablythe 15
- 16. @ablythe Mark Burgess ❖ “Every time someone logs into a system interactively, they compromise everyone’s knowledge of that system” 16
- 17. @ablythe Pipeline Rules ❖ Build binaries only once ❖ Separate environment specifics ❖ Deploy the same way in every environment ❖ Smoke test your deployments ❖ Deploy into a copy of production ❖ Each change should propagate through the pipeline instantly ❖ If any part fails, stop the line 17
- 18. @ablythe 18
- 19. @ablythe Thoughtworks Continuous Integration Rules ❖ How to Do It ❖ Developers check out code into their private workspaces. ❖ When done, the commit changes to the repository. ❖ The CI server monitors the repository and checks out changes when they occur. ❖ The CI server builds the system and runs unit and integration tests. ❖ The CI server releases deployable artifacts for testing. ❖ The CI server assigns a build label to the version of the code it just built. ❖ The CI server informs the team of the successful build. ❖ If the build or tests fail, the CI server alerts the team. ❖ The team fix the issue at the earliest opportunity. ❖ Continue to continually integrate and test throughout the project. ❖ Team Responsibilities ❖ Check in frequently ❖ Don’t check in broken code ❖ Don’t check in untested code ❖ Don’t check in when the build is broken ❖ Don’t go home after checking in until the system builds 19
- 20. @ablythe Three Things to Get Right •Culture •Workflow •Tooling 20
- 21. @ablythe Part 1 Culture 2. Workflow 3. Tooling 21
- 22. @ablythe 22
- 27. @ablythe Adrian Cockcroft - Formerly Netflix 27
- 28. @ablythe Michael McGarr - Currently Netflix 28
- 29. @ablythe Lean Enterprise “The long-term value of an enterprise is not captured by the value of its products and intellectual property but rather by its ability to continuously increase the value it provides to customers-and to create new customers-through innovation.” 29
- 30. @ablythe 30
- 31. @ablythe Mission Control vs. Command and Control The Prussion Army lost to Napoleon in 1809 Picture courtesy: http://en.wikipedia.org/wiki/Prussian_Army 31
- 33. @ablythe 2014 State of DevOps Report 9,200 technologists 33
- 34. @ablythe ❖ I would recommend this organization as a good place to work. ❖ I have the tools and resources to do my job well. ❖ I am satisfied with my job. ❖ My job makes good use of my skills and abilities. 34
- 35. @ablythe 35
- 36. @ablythe 36
- 37. @ablythe Part 2 Workflow 3. Tooling 1. Culture 37
- 38. @ablythe 38
- 39. @ablythe 39
- 40. @ablythe 40
- 41. @ablythe 41
- 42. @ablythe 42
- 44. @ablythe Steve Yegge’s Rant - Summary of Jeff Bezos ❖ 1) All teams will henceforth expose their data and functionality through service interfaces. ❖ 2) Teams must communicate with each other through these interfaces. ❖ 3) There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network. ❖ 4) It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom protocols -- doesn't matter. Bezos doesn't care. ❖ 5) All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. ❖ 6) Anyone who doesn't do this will be fired. 44
- 45. @ablythe What does that last slide mean? ❖ API!!!!!! 45
- 47. @ablythe ❖ So when can you say you’re doing continuous delivery? I’d say it’s when you could flip a switch to go to continuous deployment if you decided that was the best way to deliver value to your customers. ❖ http://continuousdelivery.com/2010/08/continuous-delivery-vs- continuous-deployment/ - Jez Humble 47
- 49. @ablythe 294 Highlights – Kindle Version ❖ It should always be cheaper to create a new environment than to repair an old one. Humble, Jez; Farley, David (2010-07-27). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison- Wesley Signature Series (Fowler)) (Kindle Location 1633). Pearson Education. Kindle Edition. 49
- 50. @ablythe Let’s Take a Test!!!!11!! If your configuration management process is sound, you should be able to answer “yes” to the following questions: ❖ Could you completely re-create your production system, excluding production data, from scratch from the version -controlled assets that you store? ❖ Could you regress to an earlier, known good state of your application? ❖ Can you be sure that each deployed environment in production, in staging, and in test is set up in precisely the same way? If not, then your organization is at risk. 50
- 51. @ablythe Gary Gruver - HP Transformation 51 https://medium.com/@aaronblythe/
- 52. @ablythe 52
- 53. @ablythe 53
- 54. @ablythe 54
- 55. @ablythe Command and Control vs. Promise Theory 55
- 56. @ablythe 56
- 64. @ablythe Part 3 Tooling 1. Culture 2. Workflow 64
- 65. @ablythe Continuous Delivery Tools Workflow PluginDelivery Many more over the next couple years… 65
- 68. @ablythe 68
- 70. @ablythe Can this actually be done? 70
- 71. @ablythe 71
- 72. @ablythe If we delivery faster so what? 72
- 73. @ablythe 73
- 74. @ablythe 74
- 75. @ablythe Key Takeaways ❖ Focus on culture first and continually ❖ Find largest outlier for lead time, automat that, repeat ❖ Use tooling the developers love and get out of their way ❖ Don’t use big bang; consider the strangler pattern ❖ Use master not branches 75