Blazing Fast Feedback Loops in the Java Universe
summary
Small Java/Groovy teams (five people, ~30 repos) shrink feedback from hours to minutes by automating concrete checks: Jenkins health check builds ping services every 5–10 minutes, GitHub Status API and branch-required-up-to-date prevent breaking master, and a company quality Gradle plugin bundles Checkstyle/PMD/FindBugs configs with clickable IntelliJ links. Builds run tests in parallel and use -Werror to fail on compiler warnings; PIT mutation coverage and nightly build matrices flag fragile tests and environment regressions so fixes arrive before they cascade.
AI-written summary · about
chapters (33)
- 0:00Intro
- 2:53CONTEXT
- 4:24BROKEN ANYTHING?
- 7:08STRUGGLING WITH TECHNOLOGY?
- 8:28STRUGGLING WITH PROJECT?
- 9:14STYLE ISSUES DURING CODE REVIEW?
- 11:31PREVENTING COMPILER WARNINGS
- 12:57DEPENDENCY UPDATES
- 14:18COMMIT MESSAGES
- 16:08BUILD STATUS
- 16:55JENKINS CI BUILD MONITOR PLUGIN
- 17:19SIREN OF SHAME
- 19:36No RED MASTER PLEASE!
- 22:25SHIELDS AND BUTTONS
- 24:14UNIT TESTS
- 26:25PARALLEL TESTS CONFIGURATION
- 27:38PARALLEL BUILD CONFIGURATION
- 29:04GRADLE PERFORMANCE TIPS
- 31:34CODE STYLE/STATIC ANALYSIS
- 35:01INTERNAL QUALITY PLUGIN
- 37:30EARLY STATIC ANALYSIS FEEDBACK
- 40:46GRADLE BASE PLUGIN
- 46:14FAST MUTATION TESTING
- 47:17NON-REQUIRED CHECKS
- 48:52PLAY WITH COMMITTING IDEA FILES
- 49:15PROVISION NODES AUTOMATICALLY
- 50:42PIPELINES
- 54:14OPEN PULL REQUESTS DASHBOARD
- 54:39CONTRIBUTING FILE
- 54:55QUALITY OF FEEDBACK
- 55:36RETROSPECTIVES
- 56:01DIALOGUE SHEETS
- 56:39SUMMARY
related talks
42mDeveloper Joy: How great teams get s%*t done
42mJenkins: Enabling Agility and Efficiency
27mDeveloper Experience: It’s Time to Start Complaining
40mAssuring top-notch code quality in the Java Universe
41mContinuous Integration Tips & Tricks
40mTightening the Feedback Loop
48mJava's Hidden Gems: Tools and Libraries
35mMassively Continuous Integration: From 3 days to 30 minutes