Upgrade to Pro — share decks privately, control downloads, hide ads and more …

From scheduled builds to commit triggered pipelines - devone 2017

From scheduled builds to commit triggered pipelines - devone 2017

Two years ago, we had the gut feeling that we had implemented a pretty solid continuous integration practice in our development lab: all our builds were automated, we were running 70,000 unit and 130,000 integrations tests per week, and sprint reviews also comprised a regular check on test coverage for new features. However, over time some problems showed: builds were getting slower and slower, it was hard to fully test features locally before committing them, and as we had so many tests it took days to get feedback for a commit. As our codebase grew, these problems gradually worsened, and developer productivity started to suffer. In this talk we will tell our story how we moved from builds and tests running on a fixed schedule in our legacy build environment towards a pipeline as code approach in Jenkins. We will talk about how we convinced our managers, the daily benefits for our developers in terms of faster feedback loop, and how we did this while ensuring we could still release working products along the way.

Wolfgang Gottesheim

June 01, 2017
Tweet

Other Decks in Technology

Transcript

  1. View Slide

  2. View Slide

  3. View Slide

  4. View Slide

  5. View Slide

  6. View Slide

  7. View Slide

  8. View Slide

  9. View Slide

  10. View Slide

  11. View Slide

  12. View Slide

  13. View Slide

  14. View Slide

  15. View Slide

  16. View Slide

  17. View Slide

  18. View Slide

  19. View Slide

  20. View Slide

  21. View Slide

  22. View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. View Slide

  27. View Slide

  28. View Slide

  29. View Slide

  30. View Slide

  31. View Slide

  32. View Slide

  33. View Slide

  34. View Slide

  35. View Slide

  36. View Slide

  37. View Slide

  38. View Slide