Scala & sbt Communities

Build Cache. Build Cache speeds up local and CI builds by allowing you to share and reuse unchanged build and test outputs across the team. The task input comparison tool helps you understand why local devs and CI builds are not benefitting from the remote build cache to maximize performance and reuse.

Predictive Test Selection. Leveraging machine learning, Predictive Test Selection can save significant testing time by identifying, prioritizing, and running only tests that are likely to provide useful feedback during test runs.

Test Distribution. This approach accelerates test execution and complements build caching while addressing many of the limitations of single-machine parallelism and CI fanout. It does this by distributing test execution work to remote executors.

Performance Continuity.  Performance Continuity  refers to a rich set of analytic, profiling,  and diagnostic tools to sustain the feedback cycle time optimizations achieved with build caching.  It includes critical path analysis to help focus performance improvements on the parts of the build that matter most.

Build Scan™. Build Scan gives Scala developers detailed data for every build, so they can quickly find the root cause of build and test failures and fix them on their own without re-running broken builds to reproduce problems. 

To facilitate debugging, build data can be filtered by timeframe (e.g., show me only builds run in the last seven days); username (i.e., the operating system user that executed the build); the name of the root project; build tool and version; custom values and tags; and the outcome of the running build.

Build Scan links can also be shared to allow remote debugging with teammates in remote working environments. With Gradle Enterprise and Build Scan you can also easily compare builds and understand the differences that lead to the same build succeeding and then failing.

Failure Analytics. Failure Analytics complements Build Scan by improving build, test, and toolchain reliability with rich failure metrics and trend data for  Scala  unit and instrumentation tests. You can use Failure analytics in combination with Build Scan to make problems like flaky tests and other avoidable failures easier to detect,  reproduce for root cause analysis, and prioritize for fixing based on an impact assessment and frequency of occurrence.

Trends & Insights.  While Gradle Enterprise helps you react to tactical performance bottlenecks and daily failures, it also enables you to respond proactively to systemic problems and longer-term performance regressions using dashboards that make key metrics and KPIs more observable and actionable.