The Develocity IntelliJ plugin seamlessly integrates Develocity and Build Scan capabilities directly into your IDE. It displays a live timeline of task execution and resource usage within your IntelliJ IDE.

Live Build Timeline

Moreover, it provides a streamlined Develocity configuration for local builds by allowing you to apply and configure the Develocity Gradle plugin to your projects, simplifying the adoption of build performance optimization and troubleshooting.

Streamlined Develocity Configuration

Installation

To install the plugin:

  1. Open IntelliJ IDEA.

  2. Go to File  Settings (or IntelliJ IDEA  Settings on macOS).

  3. Navigate to Plugins.

  4. Select the Marketplace tab.

  5. Search for "Develocity".

  6. Click Install next to the "Develocity" plugin and restart your IDE when prompted.

Plugin Installation

Quick Start

To use the live build timeline, the plugin requires the Develocity Gradle plugin 4.1 or newer to be manually applied or auto-injected into your Gradle build.

To manually apply the Develocity Gradle plugin, add the following to your settings file:

settings.gradle.kts
plugins {
    id("com.gradle.develocity") version("4.2.2")
}

develocity {
    // configuration
}
settings.gradle
plugins {
    id "com.gradle.develocity" version "4.2.2"
}

develocity {
    // configuration
}

You are now ready to use the plugin.

For additional details on the Develocity Gradle Plugin, refer to the Develocity Gradle Plugin User Manual.

If your build doesn’t apply the Develocity Gradle plugin, you can configure auto-injection right from within IntelliJ.

Usage

Live Build Timeline

Start a Gradle build from within IntelliJ IDEs (e.g., Gradle sync, or run a test that delegates to Gradle).

Observe the live timeline and resource graphs appearing directly in your run window (or the build window for Sync).

Plugin Usage

Individual task can be hovered to see more details, such as the task type, duration and potential non-cacheable and out-of-date reasons.

The build phase is displayed and updated while the build is running, with the following values: Initialization → Configuration → Execution → End of build → Success / Failed / Interrupted.

Build Scan publication

(requires Develocity Gradle plugin 4.1.1+)

When your build publishes a Build Scan to a Develocity instance, a notification appears in the bottom-right corner of your IDE, allowing you to open the Build Scan in your browser, or copy its URL. You can also access your Build Scan via a button in the timeline view, or directly to a given task via its popup menu.

Accessing the published Build Scan for the build

Configuration

There are three ways to configure this plugin for auto-injection (where the Develocity Gradle plugin is applied for you):

  1. Without Build Scan - Reports aren’t published.

  2. With Develocity - Reports are published to your Develocity instances.

  3. With scans.gradle.com - Reports are published to scans.gradle.com.

Navigate to the settings screen:

  1. Go to File  Settings (or IntelliJ IDEA  Settings on macOS).

  2. Navigate to Tools  Develocity.

  3. Select "Configure Develocity Integration" to enable auto-injection

Plugin Configuration

Without Build Scan

If you don’t want to publish Build Scan reports, simply enable auto-injection and specify the Develocity Gradle plugin version without specifying a server or accepting the terms of use.

With Develocity

To publish Build Scan reports to an existing Develocity instance, set the server URL to its location and specify the Develocity Gradle plugin version.

If necessary, check the Gradle plugin user manual for instructions on authenticating.

With scans.gradle.com

To publish Build Scan reports to scans.gradle.com, agree to the terms of use and specify the Develocity Gradle plugin version.

Troubleshooting

Live Build Timeline shows no data

  • Symptom: The timeline view displays a message like "Something went wrong and no data was received from the build."

  • Cause: The Develocity IntelliJ plugin is not receiving data from the Develocity Gradle plugin. This typically happens if the Gradle plugin version applied to your build is older than 4.1.

  • Solution: Ensure your build applies Develocity Gradle plugin 4.1 or newer.

Live Build Timeline is affecting the performance of my machine

  • Symptom: CPU usage spikes when the timeline view is visible.

  • Cause: The timeline view might repaint too frequently for the capabilities of your machine.

  • Solution: Go to Help  Find Action, and type Registry to open the IDE registry. Then look for the key com.gradle.develocity.ide.timeline.refresh.millis. You can specify any value between 10ms and 5000ms. Try a bigger value to reduce the performance impact of the timeline view.

Appendix A: Release history

1.0.2

27th October 2025

  • [NEW] The timeline and resource usage graph heights are now controlled by a split pane

  • [NEW] The rendering performance of the UI has been improved

  • [NEW] The timeline refresh rate can now be configured, between 10ms and 5s, with a default of 500ms, by changing the registry key com.gradle.develocity.ide.timeline.refresh.millis

  • [NEW] Y-axis labels for the resource usage graph have been replaced by a horizontal line following the mouse cursor

  • [NEW] The auto-scroll behavior is now reflected in the UI, by making the "Scroll to End" button selected when auto-scroll is enabled

  • [FIX] The timeline doesn’t render correctly when changing the IDE zoom level

  • [FIX] The "Powered by Develocity" logo can obstruct other UI elements

1.0.1

29th September 2025

  • [NEW] Avoided tasks are now shown in gray

  • [NEW] The timeline task popup can accommodate larger content before scrolling

  • [FIX] The specified Develocity URL isn’t always used for publishing a Build Scan

  • [FIX] The --rerun-tasks and upToDateWhen=false out-of-date reasons are incorrectly reported

  • [FIX] Scrolling up shouldn’t stop automatic scrolling to the current time, if active

  • [FIX] The timeline "Fit To Screen" functionality doesn’t always work for long builds or very fast builds

  • [FIX] The color of a finished task sometimes doesn’t update properly

  • [FIX] On macOS, cmd+wheel isn’t triggering a zoom action

  • [FIX] On macOS, pinch-to-zoom gesture leads to an exception

1.0.0

8th September 2025

  • [NEW] When the build publishes a Build Scan, show a notification and an action button on the Timeline to navigate to the Build Scan (Develocity Gradle plugin 4.1.1+)

  • [NEW] When the build publishes a Build Scan, individual tasks also link to the corresponding task in the Build Scan. (Develocity Gradle plugin 4.1.1+)

  • [NEW] The task type, cache key and potential non-cacheable reason and out-of-date reasons are displayed in the timeline view

  • [NEW] The task color is based on its state (Running, Successful, Failed)

  • [NEW] The build phase (Initialization, Configuration, Execution, End of Build) is now displayed in the status bar of the timeline view

  • [NEW] General UI and Look & Feel improvements

  • [FIX] Android builds triggered via Android Studio "run" doesn’t show the timeline #1

  • [FIX] The timeline doesn’t start at the build start time

  • [FIX] Zooming doesn’t work correctly in some cases

  • [FIX] The task path is not visible when the task started outside the visible area

0.5.1

23rd July 2025

  • [FIX] IntelliJ hangs when trying to open the timeline view

  • [FIX] The Develocity Gradle plugin version requirement isn’t sufficiently visible to users

  • [FIX] Failure when opening documentation on Linux

0.5.0

11th July 2025

  • [NEW] Live timeline view for Gradle builds

  • [NEW] Streamlined Develocity configuration