Cut debugging time by up to two‑thirds with
Developers can spend hours troubleshooting broken builds, and the process can be slow and frustrating. Gradle Enterprise Build Scan gives you granular analytic information for every build, so you can quickly fix problems and debug performance issues. When you need help, sharing deep links to specific Build Scan report elements makes collaboration easy. Gradle Enterprise Build Scan supports Gradle, Maven, and Bazel build tools.
Key Build Scan™ Benefits
Troubleshoot failures faster
Minimize the time to troubleshoot a failure by accessing relevant data that helps to determine the incident’s root cause quickly.
Collaborate more efficiently
Enable a self-service culture by empowering developers with data and collaborative tools to solve build problems without involving the CI or build team.
Speed up builds and tests
Identify slow operations and cross-reference with Build Cache and environment information to reduce feedback time.
Start now and create your first Build Scan in 30 seconds using our FREE Build Scan service or take advantage of the secured self-hosted instance provided within Gradle Enterprise. This short video will show you how easy it is to configure the Build Scan service for Gradle and Maven builds.
Compare FREE Build Scan and Gradle Enterprise Build Scan
Complete support for all individual Build Scan build data profiles and reports
Unlimited number of scans
Shareable deep link support to quickly collaborate on platforms such as Stack Overflow
Retention of Build Scan data
Support for “Build Comparison” and “Similar Failures” features
Airgapped build and test data never leaves your network (stored behind the corporate firewall)
No email registration requirement to run each individual Build Scan
Enterprise REST API allows Build Scan data integration with BI/reporting tools of choice
Note! While the FREE service can help you troubleshoot failures, Gradle Enterprise also uses Build Scan data in conjunction with Gradle Enterprise Performance Acceleration solution technologies to tune performance outcomes, and supplement our Failure Analytics capabilities.
Launch your first Build Scan now!
Key Build Scan Features
|Compare scans to pinpoint failure root cause||Collaborate effectively||Leverage an enhanced console log|
|Perform diffs between two builds to quickly determine what exactly changed since the last successful build to pinpoint what most likely broke the build. Build Scan Comparison shows differences in the build environment, dependency trees, and metadata between builds.||Collaborate seamlessly with colleagues by sharing any detail of a Gradle, Maven, or Bazel Build Scan using a deep link (e.g., even down to a single line in a console log). Integrations with Jenkins and TeamCity facilitate collaboration and workflow with CI teams.||Filter by task paths and task types for Gradle builds or goal execution and goal name for Maven builds. Filter raw log data, download log data, and share details with colleagues easily.|
|Discover dependency-related failures||Detect and correct deprecations||Use the plugins list view to assist in debugging|
|Navigate between a dependency and a repository view, traverse dependencies, view details via pop-outs, collapse and expand the dependencies graph, search dependencies via keywords, and navigate the multiple filtering options to find failure root causes.||Drill down into specific build actions that use deprecated components, find build action details within the context of your build, easily view documentation that explains the deprecation, and share the details with your colleagues.||Facilitate plugin-related debugging with the ability to search plugins by name or project, and quickly access plugin version, type, and usage pattern information. This is particularly useful when trying to identify third-party plugins and assess them for potential security risks.|
|Expand Build Scan data with custom values & tags||Utilize switch and infrastructure data||Export Build Scan data with Enterprise REST API|
|Include additional relevant troubleshooting information, such as domain-specific details and more CI environment properties, using custom values and several searchable tag types.||View build platform switch parameters and infrastructure settings that capture the specifics of the build environment (such as the OS, JDK, and locale), along with convenient links to useful documentation related to build failures.||Integrate Build Scan metric and other data with BI/monitoring tools like Tableau for companies that use a different system of record to consolidate data for executive reporting. The API uses the OpenAPI spec and comes with sample code for data models and client apps.|
|Assess test performance||Analyze feedback speed||Get a timeline view of your build|
|View the details of a failed test method, get an overview of test status, search and filter tests, and share information about tests you are investigating. Failed tests can be analyzed to quickly determine the root cause by viewing the stack trace and output, as well as the historical and visual trend data.||View task and goal execution, performance details resource utilization, caching, build configuration, and network activity. Users can leverage this information to make decisions about build performance and gauge the impact of various aspects of the build process.||Get a friendly visual overview of executed build actions to determine where the build is spending most of its time and resources and to understand the implicit/explicit task dependencies. You can also filter by the outcome of the build action, which is helpful in failure analysis.|
Build Scan™ Comparisons in Action
Compare two builds to find issues quickly