A Committer's View on Eclipse Automated Error Reporting - EclipseCon Europe 2018

Transcript

1. KARSTEN THOMS A COMMITTER’S VIEW ON ECLIPSE AUTOMATED 
 ERROR REPORTING https://pixabay.com/de/banner-kopfzeile-k%C3%A4fer-insekten-1711719/
2. About • Since 2003 @itemis • Specialized in Language Engineering, Toolchain Development, DevOps • Eclipse Committer since 10 years • Committer on Xtext, Platform, PDE • Contributor for JDT, CDT, Oomph, EMF, Tycho, EGit, Equinox, MWE, SWT • Open Source & Eclipse Evangelist @kthoms @itemis @EclipseCon #EclipseAERI
3. LOOKS FAMILIAR ?
4. ECLIPSE AUTOMATED ERROR REPORTING • Introduced with Eclipse Mars • Provided by CodeTrails • Current Metrics: • 160 Eclipse Projects enabled • 71k Problems, 47k UNRESOLVED • 2.7 Mio Incidents
5. FEEDBACK TO USER
6. BUT HOW THIS WORKS FROM COMMITTERS VIEW ?
9. AERI https://dev.eclipse.org/recommenders/committers/aeri/v2 THE ECLIPSE AUTOMATED ERROR REPORTING CLIENT
12. XTEXT
17. Possibly sensible data
18. Low Hanging Fruits Let’s pick some! https://pixabay.com/de/apple-baum-garten-gr%C3%BCn-obst-970352/
19. EXAMPLES • Example 1: NPE in SmartImportWizard • Example 2: NPE in TextSelectionNavigationLocation
20. POSSIBLE ENHANCEMENTS • Relate the incident on the Problem page to concrete platform version • Link to source • Linking multiple problems to one bugzilla ticket also in bugzilla ("See also" link) • Search similar problems which deduplication did not detect (improve manual deduplication)
21. CONCLUSION • Dramatically reduces effort for users to report issues • Possible to focus on the errors that many users are facing • Easy to pick Low Hanging Fruits • Consequent working on reported issues improves stability of the platform
22. WANT TO USE FOR YOUR OWN PRODUCT?