Introducing DPE University — Explore free, self-paced training courses on Gradle and Maven
Logo

Build Scan

Overview

Get granular information for all local and CI builds using Gradle, Maven, Bazel, and sbt. Quickly troubleshoot failures, identify root cause, compare builds, debug performance issues, and collaborate.


Developers can spend hours troubleshooting broken builds, and the process can be slow and frustrating. Develocity 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. Develocity Build Scan supports Gradle, Maven, and Bazel build tools.

Key Benefits

  • Troubleshoot failures faster: Minimize the time to troubleshoot a build failure or software testing 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.

Key Features

  • Compare Build Scans: 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 & search easily: 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). CI system integrations facilitate collaboration and workflow with CI teams. Leverage Build Scan's advanced query language.

  • Leverage an enhanced console log: 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: 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.

  • Detect and correct deprecations: 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.

  • Use the plugins list view to assist in debugging: 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: Include additional relevant troubleshooting information, such as domain-specific details and more CI environment properties, using custom values and several searchable tag types.

  • Utilize switch and infrastructure data: 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.

  • Export Build Scan data with Enterprise REST API: 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: View the details of a failed software testing 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.

  • Analyze feedback speed: 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 timeline view of your build: 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.