Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Jenkins in the real world - DevOpsCon 2017


Published on

There are a lot of Continuous Integration services but Jenkins is still one of the most used in most programming languages. In this talk I will share the CurrencyFair experience, how our IT Team made of 40 engineers manage CurrencyFair delivery with GitHub, Jenkins, Hubot and Slack on different environments. Artifact to guarantee the stability of your codebase, pipeline and some Jenkins’s plugins in order to create the most comfortable delivery flow for your projects.

Published in: Technology
  • Be the first to comment

Jenkins in the real world - DevOpsCon 2017

  1. 1. Continuous Delivery with Jenkins in the real World @gianarb
  2. 2. We don't Install a new Jenkins server
  3. 3. We don't understand how works a specific plugin
  4. 4. Continuous delivery vs Continuous deployment
  5. 5. Deploying major new features to production should be as easy as starting a flamewar on Hacker News about spaces versus tabs. Zach Holman
  6. 6. Stay focused on your business
  7. 7. Your business is moving code between servers.. I don’t think so.
  8. 8. Reduce human errors
  9. 9. keep developers focused.
  10. 10. Terminology ● Release ● Artifact/Artefact ● Pipeline ● Continuous delivery ● Continuous Integration ● Continuous deployment ● Rollback ● CI server ● Job
  11. 11. 1. Unique pipeline There are a lot of rules but all projects and all teams are different, study and build the best pipeline for your project and your team.
  12. 12. 2. face the front but don't forget the past The new code is awesome but your pipeline must work also during a disaster
  13. 13. 3. Speedy in 1 minutes I can maintain the focus on the execution but 15 minutes are a lot, you can take a coffé or start to think about another task. Return back to your old task requires some effort.
  14. 14. 4. Reproducible make, ant, grunt make your pipe easy to reproduce outside the runner
  15. 15. 5. Versionable The history of your pipeline it's important, try to maintain it
  16. 16. 6. Track! Track! Track! Monitor the productivity and mark your important steps
  17. 17. 7. Communication layer Create the best communication flow between your continuous integration system and your team, your goal is disable the Jenkins UI Only for strong hearts
  18. 18. Create strong integration Work hard to maintain your pipeline efficient
  19. 19. T-shirt time
  20. 20. Your CI server is the unique door to production. ● monitor ● logs ● recovery ● HA ● scalability ●
  21. 21. Jenkins supports Master/Slave scalability. You can distribute builds across different nodes.
  22. 22. Backup/Restore policy What will we do during a disaster? Are we able to recover? I backup JENKINS_HOME excluded plugins. There are plugins to backup if you need.
  23. 23. Pipeline as code
  24. 24.
  25. 25. Hubot -
  26. 26. Blueocean -
  27. 27. Plugins as code pluginID:version credentials:1.18 maven-plugin:2.7.1 ...
  28. 28. Plugins as code
  29. 29. Thanks a lot Site Reliability Engineer at InfluxData. Open source maintainer and Docker Captain @gianarb see you here! 6.15pm to speak about Docker security!