Successfully reported this slideshow.
Your SlideShare is downloading. ×

How to keep Jenkins logs forever without performance issues

How to keep Jenkins logs forever without performance issues

Download to read offline

Jenkins is a golden source of information: it contains logs, artifacts and feedback and x-refs from multiple sources. To keep our master healthy and responsive, often we need to remove precious data. The members of the Gerrit Code Review project wanted to keep everything and this is how we did it.

Jenkins is a golden source of information: it contains logs, artifacts and feedback and x-refs from multiple sources. To keep our master healthy and responsive, often we need to remove precious data. The members of the Gerrit Code Review project wanted to keep everything and this is how we did it.

More Related Content

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

How to keep Jenkins logs forever without performance issues

  1. 1. Jenkins Forever Never delete anything and keep optimal speed Luca Milanesio - GerritForge luca@gerritforge.com
  2. 2. About GerritForge • Born 8 years ago in the UK • HQ in London, Offices in the USA, Italy, Germany • Committed to OpenSource
  3. 3. Agenda • Using Jenkins for Gerrit Code Review • The broken links problem • What the people wants • Our solution • Your solution • Q&A
  4. 4. gerrit-ci.gerritforge.com
  5. 5. Our pipeline Verifier flow One or more patchsets pushed
  6. 6. Our pipeline Verifier flow Verifier change Verifier change Parallel jobs triggered for each change
  7. 7. Our pipeline Verifier flow Verifier change Verifier change Bazel buildsBazel buildsBazel buildsBazel builds Gerrit parallel builds (modes and validations)
  8. 8. Our pipeline Verifier flow Verifier change Verifier change Bazel buildsBazel buildsBazel buildsBazel builds Results notified and backlinks created
  9. 9. Our numbers 300 jobs 170,000 builds 4.8 Millions of jar artifacts 1.7 Billions lines of logs
  10. 10. Jenkins and the filesystem problems • Everything is a file • Jenkins needs time to read them • Filesystem inefficiency • Disk-space limits
  11. 11. Current Jenkins solution Support.Cloudbees.com http://goo.gl/x2TQxq
  12. 12. Really? • Logs are value • Would you destroy your cash … because you wallet is too small?
  13. 13. The broken link problem
  14. 14. What people wants 1. Keep everything on-line 1. Keep Jenkins speed 1. No more broken links
  15. 15. Our solution
  16. 16. Q&A What is YOUR solution?
  17. 17. AOB / Q&A www.gerritforge.com/contact
  18. 18. What to know more about Gerrit? London – UK 2-3 October 2017 http://GerritUserSummit.eventbrite.com

×