Changing one dependency declaration can have unexpected side effects through its transitive dependencies. For an example of tightly-coupled dependencies, let’s look at a simple Spring Boot project with the following build.gradle file.
Have you ever had an infrastructure failure break your build, or perhaps been forced to stop working in order to fix broken build configuration? Changes to development infrastructure often happen unbeknownst to the engineers it serves. Many problems go unreported, but chip away at our productivity much more than we realize. It is important to identify and stop non-verification failures (those not caused by routine development, such as compile and test failures) before they disrupt your organization. To combat this, we are pleased to introduce new failure analysis tools.
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.
We found out that compilation speed is not affected much by instance size, while the price doubles with every step. The most cost-effective instance is thus m5.large (2 cores). But what happens when we throw in our Hydra parallel Scala compiler?
Do you ever watch your IDE sync or build run and think to yourself: “This is slow. I think this used to be much faster”? I do, more often than I’d like to admit.
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.
We ran a number of Scala compilation benchmarks and look at what instance type is the fastest and what offers the best cost per build. We also checked the speed improvements in the latest 2.12.8 release, so read on for the full story or jump to Conclusions for the tl;dr;
Build cache infrastructure can be critical to accelerate your builds. But don’t expect to achieve your maximum potential build acceleration right out of the box.
Hell has frozen over. Develocity supports Apache Maven!
