SESSION

Harnessing Data for DevProd Decisions: A Case Study

Build Scan and Develocity are game changers in collecting data on key elements of developer productivity: building and testing code. This innovation lies in the seamless integration of data collected from continuous integration environments with data collected from developer environments. For the Gradle Build Tool project, this represents more than a million Build Scans retained in the public Develocity instance at https://ge.gradle.org.

Some of that data is leveraged to show the different Develocity screens. But the system contains so much more data. What can we learn from it? What kind of analysis can we run on it?

In this session, we will explore how the Gradle Build Tool Engineering team leveraged the data collected on https://ge.gradle.org to identify potential issues, measure the impact of changes, and confirm that they have a positive effect.

What did we improve? What surprised us? Join this session to discover the answers to those questions.

View the slides Arrow Down
PRESENTED BY
  • Company Logo

    Louis Jacomet

    Senior Lead Software Engineer @ Gradle

Watch Video

Watch the video Play Button

View the slides Arrow Down
Develocity Highlights

Take it further with Develocity

This session walks through how the Gradle open-source project leverages Develocity Reporting and Visualization to monitor and improve its build setup. You’ll get the key learnings from looking at the data collected from developer and CI builds, aggregated thanks Develocity.

Learn more Arrow Right

The slides

Slide 0Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24Slide 25Slide 26Slide 27Slide 28

Meet the speaker