Incredibuild Build Acceleration

Build your Rust/Cargo project through Incredibuild directly from RustRover (or IntelliJ IDEA Ultimate with the Rust plugin), via a dedicated Incredibuild menu.

Incredibuild is a build acceleration tool that distributes compilation work across the free cores of multiple machines on your network (or in the cloud), cutting build times without requiring any changes to your code or project structure.

Features

The Incredibuild menu (next to Build in the main menu bar) provides:

• Build - builds whatever the IDE's own Build Project would build, through Incredibuild
• Rebuild - cleans the Cargo workspace first, then builds it
• Stop Build - cancels the build in progress

The accelerated build runs the same cargo command the IDE itself would have run, so the selected run configuration, build profile and target selection are all respected.

Accelerating the IDE's own build actions

The IDE's build actions can be accelerated too, in RustRover, CLion and Rider. Turn on Accelerate the IDE's own build actions under Settings/Preferences > Tools > Incredibuild, and the IDE's standard Build and Rebuild go through Incredibuild - whether started from the Build menu, the toolbar or a keyboard shortcut - and so does the build a run configuration performs before it starts. The commands and keyboard shortcuts stay exactly where they are; only what happens underneath changes.

• RustRover: Build Project / Rebuild Project, and the build before Run and Test. These report into the IDE's own Build tool window.
• CLion: Build and Rebuild of the selected target, Build Project / Build All, and a CMake run configuration's Build step. A rebuild becomes cmake --build --clean-first.
• Rider: Build Solution (including the toolbar's Build button and its shortcut, when it builds the solution), Rebuild Solution, Build Selection in the Solution Explorer, and a run configuration's Build Solution / Build Project step.

In every IDE, when one of the IDE's own builds is accelerated, it reports into the IDE's Build tool window, just as a local build does: its output live, with progress (Ninja's and Make's step counts, MSBuild's finished projects) while it's distributed; each compiler error and warning in the build tree, clickable through to its file and line (as are the file locations in the output); and the result and how long it took. The Build tool window's stop button stops the Incredibuild build cleanly, as Stop Build does.

The setting is off by default, and while it is off those actions behave exactly as they do without this plugin. With it on, a build that can't be accelerated falls back to a standard local build rather than failing, and a notification says why: Incredibuild isn't installed, isn't licensed to start builds on this machine (checked on Windows), its version is older than the minimum supported one, or - in CLion - the active CMake profile uses a remote (WSL, Docker, SSH) toolchain. Actions that have no Incredibuild equivalent - Clean, Install, recompiling a single file, Rider's per-project build modes - always run as the IDE's own. The actions in the Incredibuild menu always use Incredibuild, whichever way the setting is set.

Rider (.NET)

In Rider, the Build menu gets dedicated Incredibuild actions right after the standard ones (they are also in the Incredibuild menu):

• Build Solution with Incredibuild - builds the solution in its active configuration and platform
• Rebuild Solution with Incredibuild - cleans and rebuilds it
• Build Selected Projects with Incredibuild - builds the projects selected in the Solution Explorer, along with the projects they reference

The same actions are in the Solution Explorer's context menu on the solution, solution folders and projects, and each can be bound to a shortcut under Settings/Preferences > Keymap (search for "Incredibuild"). They have no default shortcuts, so none of Rider's own are taken over.

They run MSBuild on the solution exactly as it is configured: the active configuration and platform are respected (for selected projects, through the solution's own project configuration mapping), and an open solution filter (.slnf) limits the build the same way it limits Rider's own. Nothing about the solution or its projects is changed. While an accelerated build runs, the status bar shows Building with Incredibuild, the Incredibuild tool window shows its output under a banner naming the configuration and MSBuild used, and a notification reports the result.

MSBuild is detected automatically: the newest Visual Studio / Build Tools MSBuild.exe with the .NET SDK component on Windows, otherwise the .NET SDK's dotnet msbuild. Rider's own MSBuild selection lives in its backend settings, which plugins can't read, so a different one can be set under Settings/Preferences > Tools > Incredibuild.

Settings

Settings/Preferences > Tools > Incredibuild shows the Incredibuild installation the plugin uses - its version and folder, and whether it's ready to build or why not (Check again looks again) - and configures the opt-in above, the number of parallel jobs (-j) accelerated Cargo/CMake builds request, and (in Rider) the MSBuild to use.

If Incredibuild isn't installed on the machine, the menu commands offer to open incredibuild.com to download it.

Requirements

• RustRover, or IntelliJ IDEA Ultimate with the Rust plugin - 2026.1 or 2026.2 (builds 261-262). The Rust plugin is released for one IDE line at a time, and this plugin depends on it, so support for a newer line follows a Rust plugin release for it.
• Or CLion 2026.1 or 2026.2, with a CMake project.
• Or Rider 2026.1 or 2026.2, with MSBuild (Visual Studio / Build Tools) or the .NET SDK installed.
• Incredibuild installed, on Windows or Linux:
  • Windows: 10.37.1 or later
  • Linux: 4.29.3 or later, installed under /opt/incredibuild

Installation

• Using the IDE built-in plugin system:

  Settings/Preferences > Plugins > Marketplace > Search for "Incredibuild" > Install

• Using JetBrains Marketplace:

  Go to JetBrains Marketplace and install it by clicking the Install to ... button in case your IDE is running.

  You can also download the latest release from JetBrains Marketplace and install it manually using Settings/Preferences > Plugins > ⚙️ > Install plugin from disk...

• Manually:

  Download the latest release and install it manually using Settings/Preferences > Plugins > ⚙️ > Install plugin from disk...

• On Windows, with an installer:

  The same release page also has intellij-ib-plugin.exe and install-intellij-ib-plugin.ps1, which install the plugin into every supported JetBrains IDE found on the machine. Close those IDEs first.

License

Licensed under the Apache License, Version 2.0. See CONTRIBUTING.md for contribution terms.