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.

Ccb1927f084f639f9e9c47c7cd2c7267?s=128

Wolfgang Gottesheim

June 01, 2017
Tweet

Transcript

  1. None
  2. None
  3. None
  4. None
  5. None
  6. None
  7. None
  8. None
  9. None
  10. None
  11. None
  12. None
  13. None
  14. None
  15. None
  16. None
  17. None
  18. None
  19. None
  20. None
  21. None
  22. None
  23. None
  24. None
  25. None
  26. None
  27. None
  28. None
  29. None
  30. None
  31. None
  32. None
  33. None
  34. None
  35. None
  36. None
  37. None
  38. None