Next Workshop: Maven Build Cache Deep Dive – June 9th (9am – 12pm PDT). Learn more and register here.
Optimize CI Cost & Resource Efficiency with
CI Build Cache & Resource Profiling
If you are responsible for CI, your goal is to optimize the speed of CI builds given compute resource and cost constraints. For Cloud hosted services (e.g. AWS deployments) with elastic usage-based pricing, the improvements you can achieve with Gradle Enterprise CI Build Cache and Resource Profiling tools translate directly and proportionately into lower invoice amounts. Frequently, this reduction more than covers the cost of your Gradle Enterprise license. For internal CI and DevOps teams, this means you can handle the inevitable growth in build demand with existing resources and avoid the expense of adding capacity.
Benefits of CI Build Cache & Resource Profiling
By making compute resources more efficient you can decrease time to deployment while minimizing costs.
Key Solution Components
CI Build Cache
Gradle Enterprise Build Cache allows CI to reuse unchanged build and test artifacts. This not only speeds up CI builds since cycles but also saves a substantial amount of compute resources. Gradle Enterprise Build Cache supports both Gradle and Maven CI builds. You can learn more about Gradle Enterprise Build Cache features here.
Resource Profiling and Avoidable Failure Prevention
Build and test configuration is often very complex and if not better optimized it will lead to inefficient test and build executions. For example, over time more and more build actions that could be cached are executed unnecessarily. Resource Profiling leverages Build Scan™ to help you identify build actions that put a lot of load on your CI infrastructure. You can use this intelligence to focus your continuous efforts to reduce loads where the impact of your efforts will be highest.
Flaky tests and other avoidable failures are not just a huge source of developer frustration and wasted time. They also consume a lot of unnecessary CI resources since all those builds that failed unnecessarily have to be run at least one more time. Gradle Enterprise provides tools for minimizing avoidable failures, and as a result, saves CI resources