Explore how Develocity helps you adopt and improve DORA capabilities, including continuous delivery, in order to achieve software delivery excellence in your organization.
This blog examines GenAI’s impacts and limitations across software delivery, highlighting the necessity of reliable and robust testing, human oversight, efficient CI/CD pipelines, and rigorous security practices. Emphasizing core DevOps practices—including continuous delivery—captured by DORA metrics, we discuss the strategies your organization must adopt to fully realize GenAI’s benefits while effectively managing its inherent risks.
The complexity of sbt can often feel like navigating a black box, especially when it comes to understanding and visualizing builds and tests. A recent Gradle webinar featuring long-time Scala veteran Iulian Dragos sheds light on this very issue: the need for more enterprise-grade tools specifically designed for Scala and sbt. This post covers the key insights from that session, focusing on how enhanced observability and build caching with Develocity for sbt can significantly increase productivity for Scala developers.
The critical missing piece in today’s CI/CD and build optimization strategies is end-to-end artifact observability across the entire software toolchain. With Toolchain Observability, engineering teams can gain real-time insights, shift-left the enforcement of software governance & compliance policies, and elevate developer productivity using a data-driven approach to decision making.
Let’s face it, slow builds are the bane of every software developer’s existence. We’ve all been there: you’re ready to push your code, but the build process takes forever. Or worse, the build fails, and you have no idea why. This kills your flow, morale, and productivity—and results in delays getting your features merged and shipped. Build performance issues can have a major impact on your team’s overall productivity. That’s where build performance observability comes in. By monitoring toolchain resource usage during your builds, you can identify bottlenecks and optimize your build process for maximum speed and efficiency.
The Android developer productivity team at Toast embarked on a journey to dramatically reduce build times caused by rapid and extensive app growth. Through a number of strategic enhancements, they achieved a remarkable 61% reduction in build times—in just a few months, they went from a build time average of 68 minutes to just 27 minutes. Find out how they leveraged Develocity to identify and tackle quick wins.
Collibra is a software company specializing in unified governance of data and AI, and the first Belgian technology company ever to achieve “unicorn” status (a billion-dollar valuation) in 2018. Collibra’s Platform brings flexible data governance, continuous quality, and built-in privacy to over 700 customers around the world.
If you’re a Java developer, chances are Maven is a core part of your toolkit. But let’s face it, managing Maven versions across different environments—your local machine, your team’s setups, and your CI/CD pipelines—can be a real pain. Inconsistent installations, manual updates, and the dreaded “it works on my machine” syndrome can all slow you down and cause unnecessary headaches. Enter the Maven Wrapper—a simple tool that transparently manages your Maven installation for you!
If you’re a regular Apache Maven™ user, you know that build times can quickly add up, eating into your development time and slowing down your feedback loop–whether you’re waiting for a local build to finish or watching a pull request inch towards merge, every minute counts. This post walks through five low-effort strategies for accelerating your Maven builds, showing a real-life example that brings a 1.5-minute build down to 7.5 seconds. These tips will help you return to what you love most—writing code!
As developers, we understand the value of data. We collect it on the performance of our applications, use it to find out how our users are behaving and how to improve their experiences, and monitor our apps to anticipate problems before they strike. However, we’re often living in a data vacuum when it comes to things that impact developer productivity and the overall experience. You need data to show what is introducing friction and toil into your job. You need data to show the risks that exist from using outdated tools. And you need data to show that your solutions can fix these issues.
Accelerate
Troubleshoot
Observe
