Developer Productivity Engineering Blog

The Apache Software Foundation (ASF) and Gradle Inc. announced last week that Gradle has entered into a collaboration with the Foundation as a Targeted Platinum Sponsor. This involves Gradle providing a free instance of Develocity (formerly Gradle Enterprise) that runs as a shared ASF infrastructure service available for use by all Apache projects and contributors. Gradle aims to scale Develocity build and test performance acceleration and failure analytics benefits across the ASF community of 320 active open-source software projects. 

As Develocity continues to scale its footprint in large deployments, enterprise expectations in areas like high availability and security continue to rise. We are pleased to introduce the newest release of Develocity 2023.3, bringing streamlined project management with project-level access control, additional cloud integration capabilities, highly available build caching, and more. Let’s delve into the new features awaiting you.

Developer Productivity Engineering (DPE) is a practice for improving developer productivity leveraging technologies—rather than exclusively relying on traditional management best practices. This includes foremost analytic technologies for observing and collecting the many metrics and indicators of the overall health of your toolchain in terms of speed and reliability. Develocity captures, records, and presents these metrics. We wanted to learn which of these metrics are the most important, so we asked our users!

In the world of software deployment, three things are certain: death, taxes, and build tool migrations. Whether it’s upgrading from Gradle 7 to 8, or moving from Maven to Gradle or back, these migrations are both essential and complex. The success of planning, implementation, and post-migration management is heavily dependent upon the quality and presentation of toolchain data available to teams before, during, and after the migration. Develocity provides a wealth of mechanisms and dashboards—as well as an Enterprise API—for collecting and presenting data essential to successful build tool migration efforts.

Flaky tests pose substantial challenges due to their unpredictable and inconsistent nature. Effectively addressing them requires a multi-faceted approach that involves the effective integration of strategy, process and resource alignment, and a deep understanding of flaky test causality. This post will walk you through this approach.

Dealing with flaky tests is a significant challenge in software development. Fortunately, tools such as Develocity can aid in tracking down and mitigating these issues. Here are five ways you can use Develocity to better manage flaky tests.

We are thrilled to announce the release of Develocity 2023.2 featuring General Availability (GA) support for the Bazel build system. This major release highlights our commitment to supporting the Bazel community, further evidenced by our recent admittance to the Bazel Products Partner program. We also announced beta support for the sbt build system, as we continue to embrace the Scala developer community.

DPE Summit is back! The only event dedicated to the practice of Developer Productivity Engineering and Developer Experience will return to The Midway in San Francisco on September 20-21, 2023. Now in its second year, the event hosts leading DPE practitioners from some of the most innovative engineering organizations. In this two-day, dual-track event, DPE and DX leaders from Airbnb, Gradle, LinkedIn, Slack, Spotify, and many more will share their perspectives and practices, success stories, and lessons learned. We’re doubly excited to have JetBrains, Meta, Netflix, and Uber join us as both sponsors and speakers.

In the arena of software development, every metric has its role to play. Among these, local build times hold a position that’s often undervalued. This critical performance indicator may have been sidelined as we transitioned to remote work. It’s time we bring it back into focus, explore its significant impact on the development process, and take action, as necessary, to improve it.