Developer Productivity Engineering Blog

Does your team suffer from long feedback times because of slow running tests? Does your CI pipeline spend several hours executing integration and system tests?

Having these tests is important but once running them takes longer than a few minutes, developers will push execution to later stages of the development cycle leading to longer feedback times. Shortening feedback cycles can save teams lots of time because there are fewer interruptions to the creative process, developers spend less time waiting for each individual build, and they spend less time debugging problems that occur from compounding changesets.

Like many companies, the software development experience at Elastic was starting to become negatively impacted under the increasing strain of slowing builds and inefficient process for testing and debugging. And, the pain was only expected to increase in line with the growth of development teams, code bases, and repositories. The cost of inaction was projected to soon become unbearable.

In this webcast, Mark Vieira, Senior Software Engineer at Elastic discusses with Gradle, Inc. CEO, Hans Dockter, how Elastic overcame the natural resistance to change their process and toolset by quantifying the Cost of Inaction and blazing a new path toward build engineering excellence.

Do you hate flaky tests? If your application interacts with browsers, external services, or has asynchronous behavior, it’s likely your team has suffered from flaky tests.

Non-deterministic tests are a ruinous infection that wastes developer time and reduces confidence in your test suite.

A fast and efficient CI pipeline can make or break your team’s developer experience and productivity. But what are the biggest determinants of CI pipeline performance? How do CI platform infrastructure and build/test performance impact each other and where should you focus your efforts?

Gradle 6.0 is the culmination of several years of innovative improvements in Dependency Management. Embracing the idea that there is more to software composition and reuse than just putting a set of jar files on the classpath, Gradle now offers a new metadata format to richly define software components that are often made up of multiple files, different variants and specific constraints on their dependencies.

Whether producing private or public components, most projects are built with multiple software libraries interacting together. Aside from knowing what to publish and how to do so, this webcast covers strategies for streamlining the publication and integration processes.

In this webinar, Hans Dockter, CEO & Founder of Gradle, talked about the emerging practice of developer productivity engineering, a discipline of using data to improve essential development processes from build/test to CI/CD.

Whether you use a mono-repository or multi-repository approach for your sources, managing dependencies is central to productivity by reusing artifacts and ensuring a quality build. A single incorrect dependency can break existing code, introduce a vulnerability or simply prevent your project from building.

Android builds can be complex and challenging to optimize, yet Android teams usually have the fewest resources to work on the build. In this webinar, Jason Schroeder from Salesforce and Rooz Mohazzabi from Gradle discuss top Android build issues an how to solve them.

Build logic can grow as complex as application logic and because of that good tooling is key for a productive build-logic authoring and maintenance experience. In this webinar, Paul Merlin and Rodrigo B. de Oliveira from Gradle explain how the Gradle Kotlin DSL leverages the Kotlin language and its great tooling to provide just that.