> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incredibuild.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build Cache - Customizing Settings Per Build

<Note>
  This feature is only available in Incredibuild's [Enterprise and Business Plans](/windows/pricing-plans) and is currently in limited availability. For more details, speak to your Customer Success Representative.
</Note>

You can override the Build Cache setting for individual builds or projects.

## Override the Build Cache Behavior for a Specific Build

Clients define which Endpoint(s) are used by default in the Agent Settings, but this can be overridden in the build command for a specific build. Flags are defined to allow you to override the build cache behavior in the [BuildConsole for Make and Build Tools](/windows/running-from-command-line), [BuildConsole for Visual Studio](/windows/build-console-cli), and [IBConsole for DevTools](/windows/ibconsole-cli-options) CLIs.

For example, if you are using the BuildConsole command to run Incredibuild for make and build tools and you want to use a remote cache, you would add the /buildcacheremoteserver=\[ip address:port] flag.

This is especially useful for CI builds, where the build command is part of the overall CI script.

## Setting the Build Cache Behavior for a Specific Project

You can also configure Build Cache behavior to match a specific project using a build configuration file. You can create a configuration file with settings for a particular project, and store the file together with the project source code. This allows you to use the same settings (e.g., a specific shared cache) consistently across multiple agents and CI machines. For details, see [Modify Settings per Build using a Configuration File](/windows/modify-settings-per-build).