In Gradle Enterprise 2021.2 we’ve added support to auto scale agents when using an elastic compute platform based on demand for how many tests there are to run. In this blog post, we’re going to show you how easy this is to set up in a Kubernetes cluster, and show how test execution times of both Gradle and Maven builds are affected in different usage scenarios.
In Gradle Enterprise 2020.5 we’ve added the missing piece to our testing product for Maven: Test Distribution (available for Gradle builds since Gradle Enterprise 2020.2). In this blog post, we’re going to connect the build of the Eclipse Jetty open source project to Gradle Enterprise. We will demonstrate how Test Distribution and Build Caching – with very little effort – reduce the total build time from over 50 minutes to about 15 minutes for a typical code change. We will also discuss potential options for reducing build time even further by optimizing the build for Test Distribution.
Gradle Enterprise 2020.2 introduces a major new feature: Test Distribution. Gradle Enterprise Test Distribution executes your existing test suites faster by fanning out test execution to as many machines as you provide.
Just like failing tests, flaky tests indicate that something might be wrong with the user-facing behavior of your product. It is important to track and fix them as soon as possible. Gradle Enterprise 2020.2 features test analysis improvements that streamline test debugging and root cause identification.
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.
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.
Today, we’re excited to announce a big step towards our mission to transform how software is built and shipped. We recognize that not all teams are using Gradle or are in a position to migrate soon. In this blog post, we’ll learn how you can utilize the insights provided by build scans and the acceleration of the build cache in Apache Maven™ builds.
Hell has frozen over. Gradle Enterprise will soon support Apache Maven™. Users will get faster Maven builds and fine-grained build analysis without having to migrate.
We are excited to tell you about some big updates to Gradle Enterprise!
