Troubleshooting Gradle and Apache Maven with Develocity

How much time do we spend daily troubleshooting our CI builds? Dependencies fail, infrastructure explodes, tests are flaky, Checkstyle turns Gandalf (“you shall not pass”), and everything “works on my machine.” Or not? There are many points of failure, and we always need proper tools.

In this talk, we will focus on developer tooling for Gradle and Apache Maven, specifically for troubleshooting and observability of local and CI builds. We will discuss Gradle features and Build Scans provided by Develocity. We will look at open-source projects using these tools and how they actually benefit from them. We will show examples from Gradle itself, Spring, JUnit, Kotlin, and other open source projects we host public instances for. Stay tuned for the interactive demo and its unplanned rapid disassembly!

P.S.: You can do the same with Bazel or sbt. Ask us how!

Transcript

1. Troubleshooting Gradle and Apache Maven Stefan Wolf Alex Semin Oleg Nenashev with Develocity
4. Hello, World! Stefan Wolf Build Scans Team / Jenkins plugins maintainer 4 Alex Semin Configuration Team / BT User Success Group Oleg Nenashev DevRel & Education Team / Dev Tools community builder
5. Async Q&A: Gradle Community Slack, Testcontainers and WireMock Slack speakerdeck.com/onenashev
6. Today, 2nd of December 6 • The Presentation and Demos - Live • Q&A after the presentation - Live • Any meetings/discussions - in Munich ◦ Share your Gradle Build Tool experiences with Alex ◦ Ask Stefan about Build Scans and Develocity ◦ Any questions about Gradle! • Later: Online meeting with other offices?
7. Talk Outline • Some Mythbusters • Intro to Gradle Builds Troubleshooting • Show & Tell for Gradle and Apache Maven 7 The information contained in this presentation and the roadmap (and the "Roadmap") is intended to outline our general product direction, which is subject to change at any time. The content provided in this Roadmap is provided for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code, or functionality and should not be relied upon in making purchasing or other decisions. The development, release and timing of any features or functionality described in this Roadmap remains at the sole discretion of Gradle, Inc. Product capabilities, timeframes and features are subject to change and should not be viewed as commitments.
8. The Elephant in the Room? Amadeus loves Apache Maven, … and we too!
10. Disclaimer 10 Gradle != Gradle Build Tool in this presentation It’s not a “Gradle vs Maven” talk Gradle is about both Maven and Gradle Build tool
11. 1 1 And we mean it Valentine Day’s post
12. +
13. 13 See ge.apache.org helps Used in Beam, Groovy, Kafka, Lucent, Pulsar, Solr, etc. • 37 onboarded projects • 31 days per week - savings from the build cache • 116 days per week - savings from all caching • 30k builds per week • 503d of total build time per week
14. What is Gradle, really?
15. 15 Developer Productivity Engineering (DPE)
18. What do Gradle users say? (*) * based on user feedback, not Android specific
19. Developer Productivity Engineering (DPE) gradle.com/ developer-productivity-engineering
20. 20 (f.k.a. Gradle Enterprise)
21. TL;DR: * we do not actually suggest moving
22. 22 https://gradle.com/develocity/
23. DevelocityTM Build Scan® “X-Ray” for Gradle, Maven, Bazel, & sbt (CI & Local) Platform Flaky Test Management Build Scan & Comparison Performance & Failure Reporting Vulnerability & Compliance Reporting Out of the Box & Custom Reporting & Visualization Test Failure Analytics Benefits Test Distribution AI-Powered Predictive Test Selection Build Cache | Developer Productivity Platform Observability & Traceability Build & Test Acceleration Faster Troubleshooting
24. We gave 20,000 developers back two hours per day by cutting Maven build and test times by over 60%. Top 3 Global Investment Bank
25. For many FOSS projects: we sponsor Develocity licenses / SaaS hosting help with optimization and DPE Maven, Bazel and sbt users welcome! gradle/develocity-oss-projects gradle/develocity-oss-projects
26. Troubleshooting Gradle
28. Source: https://www.brainyquote.com/quotes/naoto_kan_510414
29. So, we… 1. Discover the issue 2. Analyze the issue 3. Apply the fix 4. Verify the issue is gone 29
30. So, we… 1. Discover the issue 2. Analyze the issue 3. Apply the fix 4. Verify the issue is gone 30 Observability
32. 32 Gradle Core Features • Gradle includes many troubleshooting capabilities • We work on improving reporting and stack traces • NEW: Problems API and reporting
33. Problems HTML Summary Report in Gradle 8.11
34. For performance profiling 34
36. Develocity | Observability is the Foundation Observe Accelerate Troubleshoot 36
38. ◦ Build Scan and Troubleshooting ◦ Local and Distributed build caching ◦ Flaky test detection ◦ Local build observability ◦ // And more! 38 for Gradle and Apache Maven Troubleshooting
39. Flaky Tests 39
40. a. Try it again b. Re-run it c. Re-run it again d. Ignore it and approve PR e. All of the above The test is flaky. What do you do now? 40
42. Flaky test handling ⬢ Detection ◦ Test retries ◦ Develocity ⬢ Flaky tests don’t fail the build ⬢ Fixing ◦ New very flaky test on the spot ◦ Regular flaky fix-it days 42
43. 43 https://ge.apache.org/scans/tests?search.buildToolType=maven&search.relativeStartTime=P28D& search.timeZoneId=Europe%2FBerlin&tests.sortField=FLAKY
44. Underutilized CPU resources 44
45. 45 https://gradle.grafana.net/d/gradle-cpu-usage/gradle-cpu-usage?o rgId=1&from=now-7d&to=now&timezone=browser
46. 46 https://ge.gradle.org/s/3spxtqmeeioze/timeline
47. Build Caching 47
48. :compileJava :compileTestJava inputs actions outputs Gradle Tasks / Maven Goals 48
49. :compileJava :compileTestJava 💻 Gradle Tasks / Maven Goals 49
50. :compileJava :compileTestJava 💻 UP-TO-DATE FROM-CACHE Build Cache Build Cache / Maven Goals 50
52. Demo Time! 52
53. Live Demo: What can we show? • Analyzing slow smoke tests • Surfacing flaky tests in the Spring Boot or Armeria • Analyzing Build and Configuration cache speed • Discovering differences on CI generated jars causing integration tests to rerun - Micronaut, / Maven • /// and More! 53 gradle/develocity-oss-projects
54. If you watch the slides offline … 54
55. Build Time Reduced by 50% & Test Time by 60% Case Studies | Netflix Total test time reduced 60% Even Faster Total test time reduced 60% Build Time Dropped 50%!
56. 110+ Days in CI and Local Test Savings with Predictive Test Selection in 30 Day Period L o c a l CI Serial testing time that could have been avoided (purple) vs unavoidable (gray) in a single day 33.3 days of serial testing time that could have been avoided if PTS was enabled 1.1M tests (42% of all tests) that could be avoided if PTS was used Local Builds CI Builds
57. 14% of builds that have had at least 1 test fail 9% of builds that have had at least 1 flaky test (same test fails then passes in the same build) Sorting by Flaky column will show the test classes with the most flaky tests Flaky and Failed Tests Identification and Prioritization
58. Test Times Before and After Develocity Test Distribution | 2 Projects Case Studies | Netflix After Test Distribution Before Test Distribution Impact ◦ (2) Projects ◦ 33 Tasks ◦ Before: ◦ 1 hour 2 min ◦ After: ◦ 4 min 59 secs ◦ Savings: ◦ 57 min 1 sec
59. The End? 59
60. What can you do? • Ask your DevEx team about Develocity ◦ Ongoing deploy/enablement • Share your feedback with us! • Learn Gradle Build Tool, Apache Maven and Develocity on DPE University 60
61. dpeuniversity.gradle.com DPE University Take a dive into Gradle! 61
62. 6 Gradle courses for all levels of experience DPE University dpeuniversity.gradle.com 62
63. dpeuniversity.gradle.com DPE University Maven & Develocity 63
64. References • Gradle Build Tool roadmap: https://roadmap.gradle.org/ • Develocity for Gradle Build Tool: gradle.com/gradle-enterprise-solutions/gradle-build-tool/ • Develocity fort Apache Maven: https://gradle.com/gradle-enterprise-solutions/maven-build-tool/ • Public Develocity instances for FOSS projects: https://gradle.com/customers/oss-projects/ 64
65. Gradle Community Slack, #developer-productivity 65 Open Questions?