O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

A DevOps Story

117 visualizações

Publicada em

This story begins on a warm day in the summer of 2014. A new team was formed to work on a critical business application. That application had few releases a year and a mile long backlog that wasn’t getting completed. Two years later, that team was has had more than 300 releases in a year.

Publicada em: Software
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

A DevOps Story

  1. 1. Jamie Phillips https://phillipsj.net Twitter: @phillipsj73
  2. 2. • Team Size • Three engineers Year Software Deployments New Apps Released 2012 ~3 1 2013 ~3 0
  3. 3. John Chase
  4. 4. In case of fire 1 git commit 2 git push 3 leave building by Marco Leong
  5. 5. • Team Size • Three engineers Year Software Deployments New Apps Released 2012 ~3 1 2013 ~3 0 2014 ~10 0
  6. 6. 1. Do you source control? 2. Can you make a build in one step? 3. Do you make daily builds? 4. Do you have a bug database? 5. Do you fix bugs before writing new code? 6. Do you have an up-to-date schedule? 7. Do you have a spec? 8. Do programmers have quiet working conditions? 9. Do you use the best tools money can buy? 10. Do you have testers? 11. Do new candidates write code during their interview? 12. Do you do hallway usability testing?
  7. 7.  Using a Hudson Bay approach to projects.  Working more closely with the operations team.  Goal was to release software every two weeks.  Automation
  8. 8. GNU Make
  9. 9.  Deployment without manual configuration  Deployed from local system
  10. 10. • Team Size • Two engineers • One SQL Developer • One Contractor Year Software Deployments New Apps Released 2014 ~10 0 2015 ~50 1
  11. 11. • Team Size • Two engineers • One SQL Developer • One Contractor Year Software Deployments New Apps Released 2014 ~10 0 2015 ~50 1 2016 ~300 7

×