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.

1. Jenkins Forever
Never delete anything and keep optimal speed
Luca Milanesio - GerritForge
luca@gerritforge.com

2. About GerritForge
• Born 8 years ago in the UK
• HQ in London, Offices in the USA, Italy, Germany
• Committed to OpenSource

3. Agenda
• Using Jenkins for Gerrit Code Review
• The broken links problem
• What the people wants
• Our solution
• Your solution
• Q&A

4. gerrit-ci.gerritforge.com

5. Our pipeline
Verifier
flow
One or more
patchsets pushed

6. Our pipeline
Verifier
flow
Verifier
change
Verifier
change
Parallel jobs
triggered for each
change

7. Our pipeline
Verifier
flow
Verifier
change
Verifier
change
Bazel
buildsBazel
buildsBazel
buildsBazel
builds
Gerrit parallel builds
(modes and validations)

8. Our pipeline
Verifier
flow
Verifier
change
Verifier
change
Bazel
buildsBazel
buildsBazel
buildsBazel
builds
Results notified and
backlinks created

9. Our numbers
300 jobs
170,000 builds
4.8 Millions of jar artifacts
1.7 Billions lines of logs

10. Jenkins and the filesystem problems
• Everything is a file
• Jenkins needs time to read them
• Filesystem inefficiency
• Disk-space limits

11. Current Jenkins solution
Support.Cloudbees.com
http://goo.gl/x2TQxq

12. Really?
• Logs are value
• Would you destroy your cash
… because you wallet is too small?

13. The broken link problem

14. What people wants
1. Keep everything on-line
1. Keep Jenkins speed
1. No more broken links

15. Our solution

16. Q&A
What is YOUR solution?

17. AOB / Q&A
www.gerritforge.com/contact

18. What to know more about Gerrit?
London – UK
2-3 October 2017
http://GerritUserSummit.eventbrite.com